maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pedro (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
Date Mon, 11 Feb 2008 07:59:28 GMT


Pedro commented on MECLIPSE-344:

I just noticed a small problem with this fix.
If you have a dependency on a project for source code and tests, the project is 
added twice to the "Required projects in the build path".
This of course causes eclipse to complain that the project has been added twice.


> 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