Bug 186244

Summary:	[WorkbenchLauncher] Eclipse does not recognize hash mark (#)
Product:	[Eclipse Project] Platform	Reporter:	Ben Tran <tranb>
Component:	Runtime	Assignee:	platform-runtime-inbox <platform-runtime-inbox>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P3	CC:	prakash, prashanthprabhu21, pwebster, sptaszkiewicz
Version:	3.2.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Ben Tran

2007-05-09 16:05:22 EDT

Build ID: M20070212-1330

Steps To Reproduce:
1.  Create a new workspace i.e C:\eclipse_3.2.2\workspace\user#2

Result:  Eclipse creates C:\eclipse_3.2.2\workspace\user
instead of C:\eclipse_3.2.2\workspace\user#2

2.  Create a new workspace i.e 
C:\eclipse_3.2.2\workspace\test2\#2user

Result: Eclipse creates the .metadata direcotry in 
C:\eclipse_3.2.2\workspace\test2 instead of
C:\eclipse_3.2.2\workspace\test2\#2user



More information:

Comment 1 Alex Blewitt

2007-05-09 18:06:48 EDT

Sounds likely. The path is probably translated to a URL, where anything after the # is considered not part of the path. The # should really be encoded with % escaping. If you replaced # with %23 in the workspace field, does that work?

Alex.

Comment 2 Kim Horne

2007-05-10 13:30:02 EDT

Oddly enough, we're not using an URL here - we're simply pumping the string into the java.io.File() constructor.

Comment 3 Susan McCourt

2009-07-15 12:38:03 EDT

"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"

Comment 4 Boris Bokowski

2009-11-26 16:33:37 EST

Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.

Comment 5 Prakash Rangaraj

2010-05-25 02:55:52 EDT

*** Bug 306688 has been marked as a duplicate of this bug. ***

Comment 6 Prakash Rangaraj

2010-05-25 03:45:13 EDT

While adjusting for the trailing slash in org.eclipse.core.runtime.internal.adaptor.LocationHelper.adjustTrailingSlash() method, the spec part after the # is eaten up. 

Moving for Platform Runtime.

Comment 7 Szymon Ptaszkiewicz

2011-08-22 09:18:42 EDT

This is a known issue and documented in the README that is shipped with the
SDK. See also bug 312772.

*** This bug has been marked as a duplicate of bug 3109 ***