Bug 489476 - Mars.2 Eclipse Restart fails to find jvm.dll when installed in a directory with a space char
Summary: Mars.2 Eclipse Restart fails to find jvm.dll when installed in a directory wi...
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Launcher (show other bugs)
Version: 4.5.0 Mars   Edit
Hardware: PC Windows 7
: P3 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-12 02:08 EST by Martin Oberhuber CLA
Modified: 2019-10-18 12:04 EDT (History)
3 users (show)

See Also:


Attachments
Screenshot of error dlg on restart (116.87 KB, image/png)
2016-03-12 02:09 EST, Martin Oberhuber CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2016-03-12 02:08:03 EST
1. Download the Mars.2 C/C++ Package for windows-x86_64 
2. Extract into a dir with space char on Win7 (D:\Eclipse\mars cpp)
3. Double click D:\Eclipse\mars cpp\eclipse\eclipse.exe -- Eclipse starts OK
4. Choose Workspace "D:\Eclipse\mars cpp\workspace"
5. Help > Install New Software , install something like PDE for example
6. Allow to restart --> error dlg "Failed to load the JNI shared library"

See attached screenshot. There is a suspicion that this problem might be related to incorrect URI encodings (https://bugs.eclipse.org/bugs/show_bug.cgi?id=214114)

Expectation is that installing Eclipse into "C:\Program Files" works flawlessly.
Comment 1 Martin Oberhuber CLA 2016-03-12 02:09:31 EST
Created attachment 260261 [details]
Screenshot of error dlg on restart
Comment 2 jan baeyens CLA 2016-03-12 06:14:57 EST
I tested on windows 10 with C++ in c:\program\files\eclipse and added PDE and that works fine.
>Expectation is that installing Eclipse into "C:\Program Files" works flawlessly.
My expectation was different but your expectation seems to be the correct one.
Comment 3 Eclipse Genie CLA 2019-10-18 12:04:30 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.