Hi, I was wondering if anyone else has experienced this and can help explain a work around or if I am missing something?
I have two Maven enabled projects in Eclipse, say A and B. Project A is a library codebase. Project B is an application that has a dependency on Project A. M2Eclipse recognises that the projects should be linked, and sets Project A as a Project dependency under the Maven2 Dependencies container for B. In the Java Build Path settings for Project A (the library), I do not have the "Maven2 Dependencies" exported. The problem comes when executing a run command (e.g. a standalone Java class / Jetty etc.) that uses the default classpath for B=2E In this case the "Maven2 Dependencies" for Project A seem to be included in the classpath IN ADDITION to the expected dependencies for project B. This seems contrary to what I would expect? I would have thought that only project B's dependencies should be included in the classpath as any other libraries required for A's use should be explicitly provided by B and/or resolved by maven and included as part of B's dependencies. This seems to cause problems when you get multiple versions of a library on the classpath and as (in my case) project A's dependencies are included first in the classpath, I have no way to get at the newer versions. Am I missing something? Thanks, Ben -------------------------------------------------------------------- mail2web LIVE – Free email based on Microsoft® Exchange technology - http://link.mail2web.com/LIVE --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
