commons-lang 2.0 is newer than 2.1?

[Matt Raible]

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)

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?

I figured the fix would be to exclude commons-lang from acegi-security:

       <dependency>
           <groupId>org.acegisecurity</groupId>
           <artifactId>acegi-security</artifactId>
           <version>1.0.1</version>
           <exclusions>
               <!-- Maven thinks 2.0 is newer than 2.1 -->
               <exclusion>
                   <groupId>commons-lang</groupId>
                   <artifactId>commons-lang</artifactId>
               </exclusion>

However, this results in both 2.0 and 2.1 being added to my WAR.

[DEBUG] adding entry WEB-INF/lib/commons-lang-2.0.jar
[DEBUG] adding entry WEB-INF/lib/commons-lang-2.1.jar

I tried adding the following to my pom explicitly, but no dice.

       <!-- Force commons-lang 2.1 for the displaytag -->
       <dependency>
           <groupId>commons-lang</groupId>
           <artifactId>commons-lang</artifactId>
           <version>2.1</version>
       </dependency>
       <dependency>
           <groupId>displaytag</groupId>
           <artifactId>displaytag</artifactId>
           <version>1.1</version>
       </dependency>

Any ideas?

Thanks,

Matt

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]