Bug 505409

Summary: Exporting RCP product to MacOS, problem with case sensitive paths in launcher binary
Product: [Eclipse Project] PDE Reporter: Dmitry Perl <dmiperl>
Component: BuildAssignee: pde-build-inbox <pde-build-inbox>
Status: NEW --- QA Contact:
Severity: major    
Priority: P3 CC: dmiperl
Version: 4.6   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X   
Whiteboard: stalebug
Attachments:
Description Flags
launcher binary none

Description Dmitry Perl CLA 2016-10-07 11:27:38 EDT
Created attachment 264689 [details]
launcher binary

I export RCP product using "Eclipse product export wizard" targeting macosx (cocoa/x86_64). Produced launcher file located under /MacOS directory contains references to the product ini file at "%s/Eclipse/%s.ini" (see attached screenshot). This breaks the application start on Mac computers with case sensitive file systems because entire package is exported under /eclipse folder while its launcher refers to /Eclipse folder. Changing the package directory to /Contents/Eclipse does solve the problem but will probably cost many people tons of hours to find out what is happening because when launched, the OS displays pretty scary error message about missing dependencies. Not worth one character typo.
Comment 1 Lars Vogel CLA 2018-12-03 09:11:12 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 2 Lars Vogel CLA 2018-12-03 09:12:06 EST
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 3 Eclipse Genie CLA 2020-11-29 09:27:13 EST
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.
Comment 4 Eclipse Genie CLA 2022-11-20 15:00:03 EST
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.