Manuel,
In this case, m2e only updates dependencies of project A (it would also
update all dependencies of projects that depend on A, if you had any).
m2e does not track dependencies of artifacts that are not present in
workspace. In your case, even if version of C changes during update of
project A, m2e is not able to detect that B requires update too. I've
looked at fixing this some time ago, but for some reason decided it was
not practical (can't remember why exactly, sorry). Please open JIRA
about this.
As usual, patches are welcome and much appreciated ;-) Workspace
resolution logic is implemented in MavenProjectManagerImpl. [1] explains
how to setup m2e development environment.
[1]
http://docs.codehaus.org/display/M2ECLIPSE/Configuring+Development+Environment
manuel aldana wrote:
hi,
got a question about transitive resolving of open projects in workspace
(could not find an entry in confluence). what happens after doing
following:
-workspace resolution is enabled
-two open projects A B, where A depends on B. B itself depends on C
which is not checked out
-doing a 'Maven->Update Dependencies' on project A.
-> transitive dep of A, in this case C is also freshly resolved
-> transitive dep of A, in this case C is not resolved
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
