[ http://jira.codehaus.org/browse/MECLIPSE-132?page=comments#action_71583 ] Jimisola Laursen commented on MECLIPSE-132: -------------------------------------------
The proposed workaround doesn't work for me. Hence, it seems to be something else causing the problem. Sadly, I haven't been able to gain much more information. However, I followed the instructions in the mailing list thread mentioned in the description and came to the conclusion that there is no significant difference between the command line when the JUnit tests runs normally and when NoClassDefFoundError are thrown. The once chance is the port and testName filename. Quite annoying bug since there isn't a known workaround. I'll be glad to investigate further if I get some instructions. > "Class not found" when run/debug JUnit tests > -------------------------------------------- > > Key: MECLIPSE-132 > URL: http://jira.codehaus.org/browse/MECLIPSE-132 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: dependency resolution > Environment: gentoo linux 2006, kernel 2.6, sun-jdk-1.5.0.06, maven > 2.0.4, eclipse sdk 3.2, myeclipse 5 m2 > Reporter: Diego Ballve > > This is for the behavior described in > http://www.nabble.com/Keep-getting-%22Class-not-found%22-when-running-debugging-JUnit-tests-tf1851758.html#a5442440 > You get "Class not found" when running/debuging JUnit tests. > For me it happened when I was importing another project and its dependencies > (both m2 projects). > Clean compile works fine, problem is with run. > The workaround to get it working is: > In the project containing your tests, edit Java Build Path | Order and > Export: Make sure M2 Dependencies appears BEFORE JRE System Library. > Thanks, > Diego -- 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
