| Summary: | [JUnit] java.lang.ClassNotFoundException: | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Lulseged Zerfu <lulseged.zerfu> | ||||||
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> | ||||||
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | |||||||
| Severity: | major | ||||||||
| Priority: | P3 | CC: | markus.kell.r, Olivier_Thomann | ||||||
| Version: | 3.6 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Lulseged Zerfu
Created attachment 170230 [details]
.classpath file
Created attachment 170231 [details]
.project file
Moving to JDT Looks like the target classpath does not contain the test class. You can see what's passed on the command line as -classpath argument when you select the process in the Debug view and then choose Properties from the context menu. In this case, I can only guess that the Maven classpath container contains entries that cannot be resolved when passed as -classpath argument. Please follow up with the providers of the Maven plug-in you're using. If they supply a special launch configuration type to run a main class from a Maven project, then they maybe also have to implement a corresponding JUnit launch configuration type (see e.g. JUnit Plug-in Test from PDE). |