[ http://jira.codehaus.org/browse/MECLIPSE-132?page=comments#action_76030 ] Brian Keyser commented on MECLIPSE-132: ---------------------------------------
Our environment is susceptible to this enviroment as well using Eclipse 3.2 and the Maven2 Eclipse Plugin 0.0.9. I have been able to create a small test case the mirrors our environment. We separate our projects into both a source and a test project. We do this because we weave different aspects in our production and test environments. However, this configuration does expose the problem. The two projects included in the following attachment are a source (maven-sample) project and a test (maven-sample-test) project. If the JUnit dependency is removed from the maven-sample project, the NoClassDefFoundError appears when attempting to run the test cases. If the JUnit dependency is present in the maven-sample project, then the test cases can be run. However, this "trick" does not work for our configuration. I was also able to get Diego's suggestion to work if I added a Maven2 Dependencies above the JRE System Library in the Classpath -> Bootstrap Entries of the target I was trying to run. However, this is less than ideal if you wish to choose a single test case to execute. > "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 > Attachments: maven-sample.zip > > > 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
