On 8/24/06, Matt Raible <[EMAIL PROTECTED]> wrote:
displaytag:displaytag:jar:1.1:compile (selected for compile)
commons-lang:commons-lang:jar:2.1:compile (removed - nearer found: 2.0)
Why is 2.0 considered newer?
It's not newer, it's nearer in the dependency graph that Maven
constructs. Run with -X and count the levels of indentation to see
why it thinks that's true.
There are some issues with dependency resolution. Your own project's
poms aren't given priority, so you can pick up the 'wrong' version of
a dependency transitively, even though it's defined correctly in your
own 'parent' pom. It just depends on "how far away" the definition is
from the basedir when you execute mvn. (So it can change depending on
where in your own project hierarchy you execute mvn.)
Also take a look at this issue that describes a problem with
dependencyManagement:
http://jira.codehaus.org/browse/MNG-1577
HTH,
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
