[
http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114636
]
Richard van Nieuwenhoven commented on MECLIPSE-344:
---------------------------------------------------
a good question! the problem is that the eclipse.workspace variable is used for
something different.
And i didn't want to break the old behavior!
Could you check if it it is still needed? maybe even deprecate it?
> 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: dependency resolution
> Reporter: Richard van Nieuwenhoven
> Attachments: 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
