Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321523 - Remove eclipse.ini from export
Summary: Remove eclipse.ini from export
Status: RESOLVED WORKSFORME
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Libra (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-02 12:17 EDT by Holger Staudacher CLA
Modified: 2022-02-24 11:24 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Staudacher CLA 2010-08-02 12:17:07 EDT 
Currently the eclipse.ini is exported with the rest of the war content. The eclipse.ini should not be contained in the exported war file.
Comment 1 Cole Markham CLA 2010-08-03 16:08:23 EDT 
If you don't include anything in the <launcherArgs> section of the product file, then eclipse.ini will not be generated.
Comment 2 Holger Staudacher CLA 2010-08-04 02:19:18 EDT 
Hi Cole,
thanks for your hint. Your absolutely right, the eclipose.ini is gone. But on the mac the eclipse.app will still be generated. It has two folders /MacOS/Content but no more eclipse.ini. So, do you know how to avoid the creation of the eclipse.app (not the Eclipse.app).
Comment 3 Hannes Erven CLA 2016-10-21 20:21:52 EDT 
I can't reproduce the issue with the current (Neon) builds.

Wild guess: your build configuration adds the .eclipseproduct file explicitly?

Since the bug was idle for almost 3 years and could not be reproduced earlier as well, I'll set it to WORKSFORME. If the issue persists, please REOPEN and attach a project that exports that extra file.