Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 424488 - Command line Mac launching does not work as before
Summary: Command line Mac launching does not work as before
Status: RESOLVED DUPLICATE of bug 424769
Alias: None
Product: EPP
Classification: Technology
Component: parallel-package (show other bugs)
Version: 4.4.0   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: 4.4.0M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-19 14:27 EST by Beth Tibbitts CLA
Modified: 2014-03-03 03:00 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Beth Tibbitts CLA 2013-12-19 14:27:33 EST
This is presumably application for all packages on Mac but I am testing parallel package.

Starting with Luna M4 (new build process; M3 worked fine)

Launching from the command line no longer works as it did before.

The Mac package no longer works when launched from the command line.
I have always done:
tar -xf foo.tar.gz
cd eclipse
./eclipse -showlocation -data /path/to/workspace

Now a popup complains "Alert  The Eclipse executable launcher was unable to locate its companion shared library.

So I like the command line invocation to keep my command lines and my workspaces straight for testing lots of builds.

Double-clicking on the Eclipse.app from the mac Finder does work just fine, however.
Which is how most folks would probably use it.

Gunnar Wagenknecht on epp-dev observed that if you instead cd to:

cd eclipse/Eclipse.app/Contents/MacOS/

Then it works as before, and he remarked "So the error message indicates that it’s having trouble finding the shared library that’s typically shipped with the executable. That’s because it doesn’t have the eclipse.ini in the "eclipse" path. However, the ini is in the Eclipse.app/Contents/MacOS folder. Thus, launching from that folder works fine on the command line."
Comment 1 Beth Tibbitts CLA 2013-12-31 00:03:34 EST
See also https://bugs.eclipse.org/bugs/show_bug.cgi?id=424769
Comment 2 Markus Knauer CLA 2014-01-30 07:42:54 EST
Setting target milestone to 4.4M6 - I didn't find the time to solve this in time for M5.
Comment 3 Doug Schaefer CLA 2014-02-10 15:38:06 EST
The 'eclipse' in the root folder is supposed to be a soft link to the eclipse int he MacOS folder. This might actually be a p2/PDE/Tycho problem.
Comment 4 Markus Knauer CLA 2014-03-03 03:00:05 EST
Confirmed it is really the missing symbolic link in the tar.gz created by Tycho:

On the server before creating the tar archive (correct):
$ ls -il eclipse Eclipse.app/Contents/MacOS/eclipse
2643298 lrwxrwxrwx 1 mknauer mknauer    34 Mär  3 07:12 eclipse -> Eclipse.app/Contents/MacOS/eclipse
2643294 -rwxr-xr-x 1 mknauer mknauer 25104 Jan 23 17:52 Eclipse.app/Contents/MacOS/eclipse

Content from the tar archive without the symbolic link:
$ ls -il eclipse Eclipse.app/Contents/MacOS/eclipse
120277 -rwxr-xr-x 1 mknauer mknauer 25104 Jan 23 17:52 eclipse
123068 -rwxr-xr-x 1 mknauer mknauer 25104 Jan 23 17:52 Eclipse.app/Contents/MacOS/eclipse

Closing this bug as duplicate of bug 424769

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