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

On 8/24/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
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 it might be hanging around in WEB-INF/lib from a prior
build.  Have you done 'mvn clean' on the entire project since changing
dependency versions?

Is this in Subversion somewhere so I can check it out and try it?

--
Wendy


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

Reply via email to