Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 306211 - OSX proper app packaging
Summary: OSX proper app packaging
Status: CLOSED DUPLICATE of bug 57349
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.6   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 11:25 EDT by adamperth81 CLA
Modified: 2010-03-28 10:49 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description adamperth81 CLA 2010-03-17 11:25:44 EDT
Build Identifier: 20100218-1602

The eclipse.app package is surrounded by all the eclipse components, eclipse.app is a directory that can contain all these components and it will be packaged like a proper osx app.

This is quite easy to do:
1. Unpack the archive
2. Move everything except Eclipse.app into Eclipse.app/Contents/Resources
3. Edit Eclipse.app/Contents/MacOS/eclipse.ini
4. Modify any paths to reference the new location inside Eclipse.app
eg:../Resources/plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
../Resources/plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.0.1.R35x_v20090707


Reproducible: Always

Steps to Reproduce:
None, OSX eclipse is just packaged wrong.
Comment 1 Remy Suen CLA 2010-03-17 11:33:22 EDT
Could be a PDE/Build thing. Releng, please advise.
Comment 2 Ralf Ebert CLA 2010-03-27 23:33:45 EDT
+1

Delivering an app file that is supposed to be dropped to the Applications folder would feel a lot more like a real OS X app. Being able to build such an .app using the PDE Build/Director tooling would also help RCP developers who are targeting OS X. Here it would especially help that internal folders are hidden from regular users behind the package.
Comment 3 Ian Bull CLA 2010-03-28 10:49:15 EDT
This turns out to be more than a packaging problem.  Moving it may work in the simple case, but there is code in the framework that assumes the exe is in a particular location. Also, p2 would need to be changed.

This sounds like a dup of bug 57349.

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