You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Gier (JIRA)" <ji...@codehaus.org> on 2009/04/03 21:26:12 UTC
[jira] Closed: (SUREFIRE-544) NoClassDefFoundError using Junit 4.3
or 4.4.
[ http://jira.codehaus.org/browse/SUREFIRE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier closed SUREFIRE-544.
------------------------------
Resolution: Not A Bug
> NoClassDefFoundError using Junit 4.3 or 4.4.
> --------------------------------------------
>
> Key: SUREFIRE-544
> URL: http://jira.codehaus.org/browse/SUREFIRE-544
> Project: Maven Surefire
> Issue Type: Bug
> Components: Junit 4.x support
> Affects Versions: 2.4.3
> Reporter: Paul Gier
> Attachments: surefire-ncdfe.zip
>
>
> This appears to be a bug in junit 4.3 and 4.4. I'm just logging it here to track it in case anyone else runs into the same problem. When two TestCase subclasses have a parent with a static initializer that throws an exception, the real error is lost and only a NoClassDefFoundError is displayed in the output. This of course made it very difficult to track down the real problem. The attached project contains a simple example that demonstrates the problem. I tested using the following versions of junit in the dependencies:
> 3.8.1 - ok
> 3.8.2 - ok
> 4.2 - ok
> 4.3 - NoClassDefFoundError
> 4.4 - NoClassDefFoundError
> 4.5 - ok
--
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