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

Bug 282221

Summary: Product export doesn't work without delta pack
Product: [Eclipse Project] PDE Reporter: Jeff Norris <jnorris>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: caniszczyk
Version: 3.5   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Jeff Norris CLA 2009-07-01 20:57:06 EDT
Build ID: 20090619-0625

Steps To Reproduce:
When I exported a product by clicking on the link in the product's editor ("Use the Eclipse Product export wizard to..."), the resulting product didn't actually have an executable inside the application bundle's Contents/MacOS directory - there's only an eclipse.ini there.  The Contents/Resources directory was also missing.  The OS gives a cryptic error if a user tries to run this exported app, saying that the application "is not supported on this architecture".

I then added the delta pack to my target platform and tried exporting again.  I just left my default architecture (macosx carbon/x86) selected on the new wizard page that was provided.  This time, the exported product had all of the correct files.

I removed the delta pack from my target platform and again the exported product was invalid.  I know that the delta pack is required for exporting to other OS's, but it seems that this bug prevents me from exporting to my own OS without the delta pack as well.
Comment 1 Jeff Norris CLA 2009-07-01 21:04:08 EDT
We just tried this out on a windows computer and had the same problem (no eclipse.exe in the deployed product).  Installing the delta pack also fixed the problem there.  This time we didn't even check the "deploy for multiple platforms" box that shows up in the product export wizard when the delta pack is installed- simply having it in the target platform was sufficient to fix the problem.

I'm removing the mac-specific notes from this bug.
Comment 2 Chris Aniszczyk CLA 2009-07-02 10:24:12 EDT
Expect to see a fix in 3.6 M1 and 3.5.1

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