Hi,
I think I had the same problem (the wrong resource was loaded).
may solution was to add an explicit version to the SureFire-Plugin
configuration:
...
2.4.3
...
See
http://www.nabble.com/%22mvn-test%22-uses-wrong-resources-to18219384.html
http://www.nabble.com/%22mvn-test%22-uses-wrong-reso
Ben Lidgey wrote:
Made the tests pass. I've no idea why. Do you want me to raise this as a
bug?
Yes... nice work! That sounds like a Core bug and not a Surefire bug, so
file it against "Maven 2" (MNG) in JIRA.
Thanks!
-Dan
--
I took a copy of the project POM and put it in the surefire-integration-tests
directory. The tests failed. I then trawled through the project POM and then
its parent POM commenting out plugins, reporting, dependencies, and other bits
until the test passed.
The thing that was causing the test t
> -Original Message-
> From: Dan Fabulich [mailto:[EMAIL PROTECTED]
> Sent: 18 February 2008 22:23
> To: Maven Users List
> Subject: RE: Surefire 2.4.1 classpath order
> [snip]
> Looks like we'll need to try some more debugging. :-)
>
> 1) If you run
> From: Dan Fabulich [mailto:[EMAIL PROTECTED]
> 2) Try pulling down our "classpath-order" test project here:
>
> http://svn.apache.org/repos/asf/maven/surefire/trunk/surefire-
> integration-tests/src/test/resources/classpath-order
> http://tinyurl.com/3csqca
>
> Run "mvn test" and confirm that y
Ken Liu wrote:
Do you know if that bug was introduced in 2.0.7 (or some other earlier
release)?
I talked about two JIRA issues; their interactions are complex.
SUREFIRE-61 is listed as affecting "2.0 (2.2 plugin)"; that means it has
probably been around for a long time. MNG-3118 is an "Impr
Dan -
Do you know if that bug was introduced in 2.0.7 (or some other earlier
release)? My team is using 2.0.4 and we encountered a problem with the
classpath ordering recently that caused builds to that were previously
working to suddenly start failing.
Thanks,
Ken
On 2/15/08, Dan Fabulich <[E
Ben Lidgey wrote:
With target/classes before targe/test-classes.
This is the reverse order from what it's supposed to be. Not only are
test-classes supposed to appear before classes, but both of those are
supposed to appear before your dependency jars.
Looks like we'll need to try some
> -Original Message-
> From: Dan Fabulich [mailto:[EMAIL PROTECTED]
> Sent: 15 February 2008 22:52
> To: Maven Users List
> Subject: Re: Surefire 2.4.1 classpath order
>
> Ben Lidgey wrote:
>
> > We are running tests using Surefire 2.4.1 and Maven 2.0.8.
&g
Ben Lidgey wrote:
We are running tests using Surefire 2.4.1 and Maven 2.0.8.
[...]
Looking at the debug output shows:
[DEBUG] Test Classpath :
[DEBUG] C:\Documents and
Settings\benl\.m2\repository\junit\junit\4.2\junit-4.2.jar
[more jars]
[DEBUG] c:\Development\Projects\MyProject\targ
On Today at 4:50pm, ak=>amit kumar <[EMAIL PROTECTED]> wrote:
ak> Hi,
ak> I have another related query regarding surefire, all of a sudden from
ak> today we started getting this error while executing JUnit tasks, the
ak> compilation of source file happens fine and the when compiling the
ak> tes
Hi,
I have another related query regarding surefire, all of a sudden from today
we started getting this error while executing JUnit tasks, the compilation
of source file happens fine and the when compiling the test source files,
the maven gives build failure telling that it was not able
to load ma
12 matches
Mail list logo
