You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Richard van Nieuwenhoven (JIRA)" <ji...@codehaus.org> on 2007/11/20 11:02:57 UTC
[jira] Updated: (MECLIPSE-344) connecting existing workspace
artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard van Nieuwenhoven updated MECLIPSE-344:
----------------------------------------------
Attachment: workspace_with_limit.patch
There are a few jira's about exluding some projects from using project references. Now this is rather easy done if the workspace is known.
I extended the patch to include the option:
-Declipse.limitProjectReferencesToWorkspace=true
This option will force projects that are not in the workspace but in the reactor to be used as jars.
this patch includes the original patch!
> 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