You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/05/14 20:02:41 UTC

[jira] Commented: (MSUREFIRE-109) [regression] Test-resources not on classpath in forkMode always

    [ http://jira.codehaus.org/browse/MSUREFIRE-109?page=comments#action_65350 ] 

Brett Porter commented on MSUREFIRE-109:
----------------------------------------

Geoffrey: I'm very confused about the results you are getting from your explanation on the usres list.

You're saying it succeeds with once and never, but not always/pertest?

In my experiment, 2.1.3 worked under all modes, while 2.2 worked under none, which is what I'd expect.

However, if I move the static block to a setUp() method, the tests pass.

Basically, we need the class to be instantiated by the classloader that will run it. I thought that would be happening.

Nevertheless, I'd highly recommend using setUp() instead of a static initializer.

> [regression] Test-resources not on classpath in forkMode always
> ---------------------------------------------------------------
>
>          Key: MSUREFIRE-109
>          URL: http://jira.codehaus.org/browse/MSUREFIRE-109
>      Project: Maven 2.x Surefire Plugin
>         Type: Bug

>     Versions: 2.2
>     Reporter: Geoffrey De Smet

>
>
> Before surefire plugin 2.2 at spring-richclient:
> -  our build succeeded
> - ValidationResultsTests worked
> - <testFailureIgnore>true</testFailureIgnore> due to an unrelated testcase: HandlerTest 
> - <forkMode>pertest</forkMode>
> Since 2.2:
> - our build failes
> - ValidtorResultTests failed too
> - while it's still <testFailureIgnore>true</testFailureIgnore> (how can it fail in that case?)
> - <forkMode>pertest</forkMode> or <forkMode>always</forkMode> (same result)
> The entire discussion (with stacktraces etc) on the user list is here:
> http://article.gmane.org/gmane.comp.jakarta.turbine.maven.user/45131

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira