[
http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126688
]
Richard van Nieuwenhoven commented on MECLIPSE-344:
---------------------------------------------------
Only linking the SNAPSHOT's, can be done, the problem is the list of options
are getting more and more complex and interweaving.
So i think it is best to make no new option but let the user decide with the
eclipse means available (what's in the workspace will be linked).
I think the best solution is to import or delete (just from the workspace) the
projects as needed and then let the eclipse plugin connect them.
> connecting existing workspace artifact-projects
> -----------------------------------------------
>
> Key: MECLIPSE-344
> URL: http://jira.codehaus.org/browse/MECLIPSE-344
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Core : 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
