You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jonathon Golden (JIRA)" <ji...@codehaus.org> on 2007/05/19 01:38:59 UTC
[jira] Commented: (SUREFIRE-116) [regression] Test-resources not on
classpath in forkMode always
[ http://jira.codehaus.org/browse/SUREFIRE-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96330 ]
Jonathon Golden commented on SUREFIRE-116:
------------------------------------------
Hi,
I tried applying Will's patch to the 2.3.1 code base and it did not solve this problem for me, however if I run my tests with Junit4 this class loader bug goes away. Perhaps the solution to the bug in the Junit3 provider can be found in the code for the Junit4 provider?
> [regression] Test-resources not on classpath in forkMode always
> ---------------------------------------------------------------
>
> Key: SUREFIRE-116
> URL: http://jira.codehaus.org/browse/SUREFIRE-116
> Project: Maven Surefire
> Issue Type: Bug
> Affects Versions: 2.0 (2.2 plugin)
> Reporter: Geoffrey De Smet
> Fix For: 2.4
>
> Attachments: JUnitTestSet.patch
>
>
> 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