[ http://jira.codehaus.org/browse/MSUREFIRE-109?page=comments#action_65353
]
Geoffrey De Smet commented on MSUREFIRE-109:
--------------------------------------------
The build doesn't break with never, I haven't tested once.
The build does break with always, even with testFailureIgnore being true.
Also as far as I can see (output + surefire report), only HandlerTest fails:
ValidatorTest works.
I've just committed the change <forkMode>never</forkMode> into
spring-richclient.
Like you recommend, I 'v changed the static contructor (which is evil anyway)
to a setUp() method.
Meanwhile something like that might be a isolated proof of concept for you guys:
public class MyTest extends TestCase {
static {
Url url = MyTest.class.getResource("myTestResource.xml");
assertNotNull(url);
}
}
> [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
