Bug 268464 - Can not start up eclipse if the parent folder name containes #
Summary: Can not start up eclipse if the parent folder name containes #
Status: RESOLVED DUPLICATE of bug 3109
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 3.5 M7   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 268109 (view as bug list)
Depends on:
Blocks: 268109
  Show dependency tree
 
Reported: 2009-03-12 22:25 EDT by Jandor Bian CLA
Modified: 2009-03-24 23:55 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jandor Bian CLA 2009-03-12 22:25:41 EDT 
Rename the eclipse parent folder name to contain a #, then eclipse can not start up. After debug we found out that there is a bug in the method buildURL() in class LocationHelper. In following code:
 if (isFile)
   return adjustTrailingSlash(new File(spec.substring(5)).toURL(), trailingSlash);
 return new URL(spec);
here we think you should use new file().toURI().toURL() instead.
Comment 1 DJ Houghton CLA 2009-03-13 09:22:55 EDT 
This is a known problem and is listed in the README file.

Tom, are we considering relaxing this restraint?
Comment 2 Thomas Watson CLA 2009-03-13 10:39:56 EDT 
This is a dup of bug 3109.  We have no plans to fix this limitation.  I will leave this open to investigate if there is an acceptable fix for 3.5 M7.  If the fix is too risky we would have to defer to the next release.  This area has proven to be sensitive to change and can easily introduce regressions.  

For example, File.toURI().toURL() would encode the special characters (e.g. space) which none of our clients are prepared to handle.
Comment 3 John Arthorne CLA 2009-03-13 11:17:41 EDT 

*** This bug has been marked as a duplicate of bug 3109 ***
Comment 4 Wei Yan CLA 2009-03-24 23:55:13 EDT 
*** Bug 268109 has been marked as a duplicate of this bug. ***