Come on guys let us not give too much attention to eachother :-)
I dont think Maven's behaviour regarding the order of JARs in the
classpath is random; that would be impossible.
My guess is the order is predictable and based on the dependencies
configuration and the algorithm that goes over it. Something like
1) Scan explicit deps
2) (Recursive?) Either
2.A) For each one add it's deps and move to the next depth level OR
2.B) Add each one, then process the next depth level of deps
3) Remove the overridden versions
This is pretty rough but you get the point. My bet is you will always
get the same classpath in a project whose POM does not change.
This of course may not provide an easy solution to the OPs prob, but the
code is OS after all so anyone is free to modify it as needed and post
patches in the JIRA or whatever :-)
Cheers,
Manos
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
