On 7 Sep 07, at 9:43 AM 7 Sep 07, Paul Gier wrote:
Hi Everyone,
I noticed that transitive dependencies seem to precede direct
dependencies on the test classpath. I created this issue related
to this:
http://jira.codehaus.org/browse/MNG-3197
Is this behaviour by design?
No. This is not good as it provides no control over ordering when you
need it. I've already run into serious issues with migrations where
you have very little control when you need it.
In the current maven, this means that if there is an older version
of one of your direct dependencies in the transitive dep tree of
another dependency, the older version will be used by the test
code. This can be confusing when a test fails because the test is
using an old version of one of the dependencies listed in the pom.
It seems like it would make more sense if the direct dependencies
take priority over transitive dependencies, but maybe there is some
reason for this. If not, I will start working on a patch to
reverse the classpath ordering.
No, what you list should be first, that only makes sense and
artifacts should not be duplicated. You are finding you're getting
two copies of foo-XXX.jar?
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
