Use eclipse artifact resolver for forked maven builds
-----------------------------------------------------
Key: MNGECLIPSE-179
URL: http://jira.codehaus.org/browse/MNGECLIPSE-179
Project: Maven 2.x Extension for Eclipse
Issue Type: New Feature
Reporter: Scott Cytacki
Assigned To: Eugene Kuleshov
Priority: Minor
We should examine if the eclipse artifact resolver, which was created to
address this issue: MNGECLIPSE-59
Should be used in forked maven builds. This would mean that artifacts would
not need to be installed into the local repository, before they could be used
by forked maven builds.
Doing this though, might have some complicated consequences. For example it
might be possible to install a project without installing a dependency. How
does the reactor handle this: if sub project A depends on subproject B can A be
installed without installing B?
That seems like a good way to think of this: the Eclipse workspace is like a
parent project that has sub projects one for each eclipse project. Just like
in a traditional multi-project, those sub projects can reference dependencies
that are not installed.
--
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
