Sounds like the depMgt issue to me...
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, February 22, 2008 4:43 PM
To: Maven Users List
Subject: RE: Compile issues after upgrading from Maven 2.0.6
I think there's a 2.0.5 to 2.0.6 upgrade guide:
3:15 PM
To: Maven Users List
Subject: Re: Compile issues after upgrading from Maven 2.0.6
Hi Everyone,
I found the root of this problem. For some reason the ClassPath order
changed in Maven 2.0.7 and Maven 2.0.8 and it exposed that an older
version
of the servlet-api code was being pulled
Hi Everyone,
I found the root of this problem. For some reason the ClassPath order
changed in Maven 2.0.7 and Maven 2.0.8 and it exposed that an older version
of the servlet-api code was being pulled as a dependency. In 2.0.7 and
2.0.8, the older version shows up first and causes the failure.
Create a sample project jar that demonstrates the problem and attach
it to a new JIRA issue.
Wayne
On 2/5/08, David Williams <[EMAIL PROTECTED]> wrote:
> Hi Everyone,
>
> I have seen this twice now so I thought I would throw this out and see if
> anyone else had seen this problem. We have two pr
