Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330113 - Executables feature including too much
Summary: Executables feature including too much
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Launcher (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-12 11:50 EST by Jeff McAffer CLA
Modified: 2019-09-17 14:27 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff McAffer CLA 2010-11-12 11:50:40 EST
the executables feature has a number of root file contributions and expectations that are not always appropriate, especially if you are doing a headless app.  Here is a starter list

- gtk : the feature brings lib_cairo as well as a set of about files that are not needed in headless scenarios
- motif : siimilarly, you get motif libs and about files
- windows : eclipse.exe (well, launcher.exe) when really it should be eclipsec.exe

A few thoughts:

- not sure if it would work... refactor the bin *launcher* entries to be WS agnostic and list these in WS agnostic root file entries.  Then have a set of root file entries as needed that bring WS-specific things like the libs and the abouts.  The tricky part might be building without a WS.

- Move the SWT-related root file and executable artifacts somewhere else.  This might be a challenge for backward compatibility

- Create a new executables feature that is just the headless stuff.
Comment 1 Eclipse Genie CLA 2019-09-17 00:25:24 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.