[ http://jira.codehaus.org/browse/MNGECLIPSE-181?page=all ]
Eugene Kuleshov updated MNGECLIPSE-181:
---------------------------------------
Assignee: (was: Eugene Kuleshov)
> Update the eclipse artifact resolver so that projects react to a change in
> one of their dependencies POMs
> ---------------------------------------------------------------------------------------------------------
>
> Key: MNGECLIPSE-181
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-181
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Task
> Components: Dependency Resolver
> Affects Versions: 0.0.10
> Reporter: Robert Elliot
> Priority: Minor
>
> Using patch project-artifacts-2006062900.patch in
> http://jira.codehaus.org/browse/MNGECLIPSE-59
> if you have project A in the workspace specifying version 0.1 of project B in
> its POM and project B version 0.1 in the workspace, this dependency of A is
> correctly resolved to the workspace. If you then change project B's POM to
> version 0.2, project A should immediately break (or resolve to the repository
> if you installed B0.1 at some point). In fact it carries on merrily resolving
> to Project B in the workspace until you make an edit to Project A's POM, at
> which point it resolves the reference to B0.1, realises it isn't in the
> workspace and acts appropriately.
> It would be nice if the plugin did a resolve of all Maven2 projects in the
> workspace when any POM is updated, to avoid this issue. Not sure how
> expensive that might be, or whether you could do a targetted resolve of only
> references to the project whose POM had changed.
> Scott Cytacki's comment:
> I agree, A should update as soon as B's pom is saved. Since m2eclipse is
> already listening to pom changes this should be straight forward. To
> optimize, each maven eclipse project can listen to all of its dependencies
> which are maven eclipse projects. We might need a new event for this, but
> hopefully there is an existing event we can use.
--
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
