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

Bug 296113

Summary:	RemotePluginTestRunner should issue better message when test plug-in not resolved
Product:	[Eclipse Project] PDE	Reporter:	Markus Keller <markus.kell.r>
Component:	UI	Assignee:	Curtis Windatt <curtis.windatt.public>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	3.6
Target Milestone:	3.6 M4
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Markus Keller

2009-11-25 09:09:33 EST

HEAD

RemotePluginTestRunner currently prints "java.lang.IllegalArgumentException: No Classloader found for plug-in org.eclipse.core.expressions.tests" when the test plug-in could not be resolved, e.g. in the scenario from bug 296105.

"No Classloader found" does not tell the user what the problem is. Could you please change the message in RemotePluginTestRunner#getClassLoader(String) to something like this, so that the user knows why this happens:

throw new IllegalArgumentException("No Classloader found for plug-in " + pluginId + " (plug-in was not resolved)"); //$NON-NLS-1$ //$NON-NLS-2$

Comment 1 Curtis Windatt

2009-11-25 11:12:04 EST

Done.

The change makes sense, I've been confused by it before.  Unfortunately, knowing that a plug-in is not resolved doesn't help me fix it.