[
https://jira.codehaus.org/browse/MECLIPSE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=288958#comment-288958
]
Demétrius Jubé commented on MECLIPSE-132:
-----------------------------------------
Well, changing the order of Maven Dependencies and JRE System Library (1st and
2nd, respectively) did the trick for me.
I'm using Eclipse 3.6.2 (Helios), and m2eclipse 0.12.1.20110112-1712.
> "Class not found" when run/debug JUnit tests
> --------------------------------------------
>
> Key: MECLIPSE-132
> URL: https://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, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
