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

Bug 129611

Summary: [JUnit] Plings "!" in filepath are not backslashed when passed to commandline
Product: [Eclipse Project] JDT Reporter: Christopher Ashley <cjashley>
Component: UIAssignee: Markus Keller <markus.kell.r>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.1.2   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug

Description Christopher Ashley CLA 2006-02-27 12:43:34 EST 
Running JUnit tests fails when the pling character !, which is a vaild character for OSX directories, appears in the path to the eclpise application i.e.

/Application/!Development/eclipse3.1.2/eclipse

When Junit test are run the console shows the errors:

Caused by: java.util.MissingResourceException: Can't find bundle for base name org.eclipse.jdt.internal.junit.runner.JUnitMessages, locale en_US

Checking the commandline arguments passed to java, the class path has the slightly incorrect entry:

/Applications/!Development/eclipse3.1.1/plugins/org.eclipse.jdt.junit_3.1.1/junitsupport.jar:/Applications/!Development/eclipse3.1.1/plugins/org.eclipse.jdt.junit.runtime_3.1.0/junitruntime.jar

The plings should have been back slashed like this:

/Applications/\!Development/eclipse3.1.1/plugins/org.eclipse.jdt.junit_3.1.1/junitsupport.jar:/Applications/\!Development/eclipse3.1.1/plugins/org.eclipse.jdt.junit.runtime_3.1.0/junitruntime.jar
Comment 1 Eclipse Genie CLA 2019-03-10 15:16:44 EDT 
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.