maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David J. M. Karlsen (JIRA)" <>
Subject [jira] Commented: (MECLIPSE-132) "Class not found" when run/debug JUnit tests
Date Wed, 05 Dec 2007 23:32:58 GMT


David J. M. Karlsen commented on MECLIPSE-132:

I do not thing this is a bug. It's a issue with eclipse not noticing that mvn has rebuilt
it all (and the old state/references in eclipse are not valid).
Pressing refresh on all the involved project solves the problem (e.g. eclipse rebuilds them).
(Running eclipse europa on jdk 1.6)

> "Class not found" when run/debug JUnit tests
> --------------------------------------------
>                 Key: MECLIPSE-132
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Dependencies resolution and build path
>         Environment: gentoo linux 2006, kernel 2.6, sun-jdk-, maven 2.0.4, eclipse
sdk 3.2, myeclipse 5 m2
>            Reporter: Diego Ballve
>         Attachments:
> This is for the behavior described in
> 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
> 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:
For more information on JIRA, see:


View raw message