You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kristian Rosenvold (JIRA)" <ji...@codehaus.org> on 2011/01/13 21:28:58 UTC
[jira] Closed: (SUREFIRE-500) puzzling NoClassDefFoundError instead
of meaningfull stacktrace
[ http://jira.codehaus.org/browse/SUREFIRE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Rosenvold closed SUREFIRE-500.
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.7.2
Assignee: Kristian Rosenvold
Fixed with integration test in r1058735
> puzzling NoClassDefFoundError instead of meaningfull stacktrace
> ---------------------------------------------------------------
>
> Key: SUREFIRE-500
> URL: http://jira.codehaus.org/browse/SUREFIRE-500
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
> Affects Versions: 2.4.2
> Environment: maven 2.0.9 , linux/ubuntu, jdk-sun-1.5.0_13
> Reporter: Johan Romme
> Assignee: Kristian Rosenvold
> Fix For: 2.7.2
>
> Attachments: surefireTest.zip
>
>
> We are using maven-2.0.9 for some project using spring/hibernate.
> When I made an incorrect change to the spring configuration (or actually I removed a hbm.xml file that was still referenced in the spring config), maven/surefire failed with an NoClassDefFoundError on one of our abstract test classes (where the spring config was loaded). Running in debug mode (-X) or increasing log4j levels did not reveal more info as to the cause of the problem.
> After some time I switched back to maven-2.0.7, maven/surefire also failed but with a meaningfull stacktrace that pointed immediately to the cause of the problem.
> So I fixed the problem, switched again to maven-2.0.9, with a succesfull build as result.
--
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