maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud Heritier (JIRA)" <>
Subject [jira] Closed: (MECLIPSE-344) connecting existing workspace artifact-projects
Date Thu, 31 Jan 2008 14:09:58 GMT


Arnaud Heritier closed MECLIPSE-344.

    Resolution: Fixed

This issue is fixed. Thanks for all patches submitted by Richard.
To try the latest SNAPSHOT (2.5-20080131.135640-18) of the incoming version you have to define
and activate this profile :
          <name>Maven Snapshots</name>
          <name>Maven Plugin Snapshots</name>
Then you have to call this command :
mvn org.apache.maven.plugins:maven-eclipse-plugin:2.5-SNAPSHOT:eclipse

> connecting existing workspace artifact-projects
> -----------------------------------------------
>                 Key: MECLIPSE-344
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>          Components: Dependencies resolution and build path
>    Affects Versions: 2.4
>            Reporter: Richard van Nieuwenhoven
>            Assignee: Arnaud Heritier
>             Fix For: 2.5
>         Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz, MECLIPSE-344.patch,
MECLIPSE-344.tgz, workspace-new-files.tgz, workspace.patch, workspace_with_limit.patch
> This patch enables you to specify your workspace, and all dependent artefacts  that are
available in your eclipse-workspace will be attached  as project references even if they are
not in the reactor.
> the property can be set with -DworkspaceToConnect=.....
> I did not have the time to create Test cases but, i maybe someone can help with that!
> The patch is based on the MECLIPSE-333 branch.
> as usual the new files are in the extra tgz.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message