[
http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116338
]
Martin Zeltner commented on MECLIPSE-344:
-----------------------------------------
After the discussion with Richie I'm convinced now that the MECLIPSE-344 covers
my needs (MECLIPSE-334) too. But dealing with files in the workspace folder
looks to me a bit dangerous because they seem to be not so stable in their
format as the .project and .classpath. Can anyone give me a link to
documentation that convince me that the amount and the formats of these files
are stable?
Cheers,
Martin
> 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: Dependencies resolution and build path
> Reporter: Richard van Nieuwenhoven
> Assignee: Arnaud Heritier
> Attachments: 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
