Bug 73071 - percent sign (%) in eclipse install folder path causes null error on eclipse startup
Summary: percent sign (%) in eclipse install folder path causes null error on eclipse ...
Status: RESOLVED DUPLICATE of bug 3109
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Rafael Chaves CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-01 11:50 EDT by Nick Boldt CLA
Modified: 2005-01-06 16:48 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Boldt CLA 2004-09-01 11:50:16 EDT
Steps to reproduce:

1. 

Installed Eclipse 3.1 into the following folder:

  E:\eclipse3.1N20040831_Reproduce_%bug\

or Eclipse 3.0.1 into this folder:

  E:\eclipse3.01%M20040825

or Eclipse 3.0.0 into this folder:

  E:\eclipse%3.0.0

2. 

Then, when running 

  E:\eclipse3.1N20040831_Reproduce_%bug\eclipse\eclipse.exe
    or
  E:\eclipse3.01%M20040825\eclipse\eclipse.exe
    or
  E:\eclipse%3.0.0\eclipse\eclipse.exe

instead of starting Eclipse, I get an alert that reads:

  An error has occurred and could not be logged:
  null
               [ OK ]

Steps to mask error:

1. 

As above, then rename the install folder to remove the '%', and the problem goes
away. 

Is this a bug? Or a 'best-practices'/'why would you use a percent sign in a
folder name?' Is eclipse trying to resolve the chars following the % as a
hexcode, such as %20 = space?

;-)

To test the above question, I tried:

  E:\eclipse%203.0.0\eclipse\eclipse.exe

as above. Now the error is different:

  An error has occurred. See the log file
  e:\eclipse%203.0.0\eclipse\configuration\1094053334197.log
               [ OK ]

So, yes, eclipse is trying to resolve the % as a hexcode. But in the examples
above %M is never going to be a hexcode... since M is not in the 0-9A-F char range.
Comment 1 Thomas Watson CLA 2004-09-02 14:01:32 EDT
I suspect this is because we use the file: URL's which get interpreted by the 
file URL handler.  My suspicion is that the file URL handler is doing the hex 
conversions.
Comment 2 Pascal Rapicault CLA 2005-01-05 16:24:54 EST
If something simple is doable we should do it, otherwise we should readme the issue.
Comment 3 Rafael Chaves CLA 2005-01-06 16:48:54 EST
Even better, it has already been readme'd!

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