[
http://jira.codehaus.org/browse/MECLIPSE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=182956#action_182956
]
Benjamin Bentmann commented on MECLIPSE-132:
--------------------------------------------
It seems you guys are reporting the issue at the wrong location. This JIRA
project MECLIPSE is about the maven-eclipse-plugin, i.e. the thing that one
invokes on the CLI like {{mvn eclipse:eclipse}}. However, you seem to have
problems with M2Eclipse, this has its issue tracker at
https://issues.sonatype.org/browse/MNGECLIPSE.
> "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: Core : Dependencies resolution and build path
> (.classpath), M2Eclipse support
> 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
