Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 323425

Summary:	No resources folder in created osx app
Product:	z_Archived	Reporter:	Henrik Lindberg <henrik.lindberg>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	P3	CC:	thomas
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X
Whiteboard:

Description Henrik Lindberg

2010-08-23 14:31:07 EDT

The create product action does not create the correct layout of the resulting osx .app folder. The "myapp.app" folder has a subfolder called Contents - this folder should have a Resources subfolder if a launcher icon (a .icns file) is specified in the launcher section of the .product definition. The Resources folder should contain the .icns file,but both folder and file are missing.

The icon specification is recognized though, as the correct entry can be found in the Info.plist file (a reference to the missing icns file).

A manual work around is to add the folder and copy of the icns file before zipping up the result.

Comment 1 Thomas Hallgren

2010-08-23 15:39:04 EDT

What happens if you try a standard PDE product export (i.e. right click, choose 'Export...' -> 'Plug-in Development' -> 'Eclipse product'). Does that product look and execute OK?

Comment 2 Henrik Lindberg

2010-08-24 17:01:48 EDT

(In reply to comment #1)
> What happens if you try a standard PDE product export (i.e. right click, choose
> 'Export...' -> 'Plug-in Development' -> 'Eclipse product'). Does that product
> look and execute OK?

Actually no - it produces an "Eclipse.app" (ie. it is not branded at all), and there is no Resources folder inside the generated Eclipse.app. The generated app does not run, when attempted I get "not supported by this architecture". I tried both generating for "multiple architectures" and selecting osx 64 cocoa, and without "multiple architectures" - both with the same result.

The only content in both cases is an eclipse.ini file.

There are no errors though, so really hard to figure out what is going wrong.

The buckminster build however does everything correct except the handling of the icns file.