I have upgraded from Maven 2.20 to 3.02, and I found many of my integration
tests that used to pass are now failing because of a ClassCastException, which
is an odd exception to find when no code has changed. I traced the issue to a
classloader problem with Maven 3 that arises in another Java
Any insight into why things work in Maven 2.20 but not in 3.02 is appreciated.
I don't believe that Maven 2.20 is a real version. Of course, 3.02
doesn't exist either, but I assume that is supposed to be 3.0.2. So
are you trying to upgrade from 2.2.0? Have you tried with 2.2.1?
Are you using
You're using an old and deprecated version of the failsafe plugin. I don't
think it works with Maven 3.
failsafe-m-p is now found at Apache Maven (not Codehaus Mojo):
http://maven.apache.org/plugins/maven-failsafe-plugin/
Upgrade and retry!
/Anders
On Fri, Jan 14, 2011 at 20:27, Neil Chaudhuri
Thanks.
-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of
Anders Hammar
Sent: Friday, January 14, 2011 4:30 PM
To: Maven Users List
Subject: Re: Classloader Problem with Maven 3.0.2
You're using an old and deprecated version
block of testing and to
create the classloader errors. Any insight is appreciated.
Thanks.
-Original Message-
From: Neil Chaudhuri
Sent: Friday, January 14, 2011 6:46 PM
To: Maven Users List
Subject: RE: Classloader Problem with Maven 3.0.2
I upgraded Failsafe to 2.7.1, and things
A closer look at the logs show that Surefire runs the unit tests, then
Failsafe runs
the single unit test configured (which fails because of the classloader
issues I
began the thread with), and then Failsafe runs all the integration tests.
Clearly something is misconfigured to cause that
