I need to have commons-lang-2.1.jar included in my WAR for
displaytag-1.1. However, Acegi Security 1.0.1 depends on
commons-lang-2.0.jar.
From mvn -X:
org.acegisecurity:acegi-security:jar:1.0.1:compile
...
commons-lang:commons-lang:jar:2.0:compile (selected for compile)
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.
I'm not sure why adding it to your POM explicitly didn't work. What
was the output of -X in that case?
-Stephen
On 8/24/06, Matt Raible [EMAIL PROTECTED] wrote:
I need to have commons-lang-2.1.jar included in my WAR for
displaytag-1.1. However, Acegi Security 1.0.1 depends on
On 8/24/06, Stephen Duncan [EMAIL PROTECTED] wrote:
I'm not sure why adding it to your POM explicitly didn't work. What
was the output of -X in that case?
If I explicitly add commons-lang:2.1 to my pom, it still includes
both. Here's the full output from maven -X package:
On 8/24/06, Matt Raible [EMAIL PROTECTED] wrote:
If I explicitly add commons-lang:2.1 to my pom, it still includes
both. Here's the full output from maven -X package:
http://rifers.org/paste/show/1593
I don't see commons-lang-2.0 at all until it's added to the WAR. Wierd eh?
It looks like
Wendy,
Your and Stephen's comments set me off on the right track. It turned
out to be caused by my common-war that was overlayed. I hadn't
installed it since I updated the parent pom.xml to exclude
commons-lang from acegi-security. Once I installed that, it solved
the problem.
Thanks!
Matt
