Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 191058

Summary:	[JUnit] JUnit launch configuration does not work in runtime workspace with binary-imported jdt.junit.runtime
Product:	[Eclipse Project] JDT	Reporter:	Markus Keller <markus.kell.r>
Component:	UI	Assignee:	JDT-UI-Inbox <jdt-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	christof_marti
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Markus Keller

2007-06-05 11:29:43 EDT

I20070605-0010, was OK in 3.2.2

Starting JUnit tests in a runtime workspace does not work if org.eclipse.jdt.junit.runtime is imported as binary in the host workspace. 

Launches fail since the Main type could not be found (because the -classpath only has "<host-workspace>/org.eclipse.jdt.junit.runtime/" but misses the jar inside). Console output:
java.lang.NoClassDefFoundError: org/eclipse/jdt/internal/junit/runner/RemoteTestRunner
Exception in thread "main" 

We probably lost this support when the jdt.junit.runtime plug-in was jarred.

Comment 1 Eclipse Genie

2019-11-10 06:35:27 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.