Just to clarify, if you changed version in pom.xml of project A, you
also need to update version of dependency in pom.xml for project B.
Workspace dependency resolution is using exact versions for matching and
if it can't find exact match in Eclipse workspace it will look in the
Maven local repository and will fail if artifact is not there and can't
be downloaded from available remote repositories (if you are not in
offline mode).
I've clarified that on the wiki at
http://docs.codehaus.org/display/M2ECLIPSE/Dependency+Management
regards,
Eugene
Igor Fedorenko wrote:
Mark,
If you expand B's "Maven Dependencies" classpath container, you can
see see if m2e has resolved B->A dependencies into A's JAR from local
repository (containers contains A-version.jar) or A project in
workspace. Can you please open JIRA with sample projects if A is
resolved from local repository.
Mark H. Wood wrote:
I have a similar problem. Eclipse 3.2.1, m2eclipse 0.9.4. I'm
working on a pair of projects thus:
o A is developed elsewhere, and I need to make minor patches to it to
support...
o B, my own creation, which depends on A.
I need to develop the patches and the new project together to the
point that I can show that my patches are acceptable for taking up
into the foreign project (A).
"Resolve dependencies from workspace" is enabled on both projects.
I removed A from my local repo, and the next time I built B I watched
Maven refill the local repo from A's remote repo.
Although I try not to disturb A except as necessary, I tried changing
its version. Building B now fails trying to download my local version
of A from the remote repo since it understandably doesn't exist there.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
