Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331595 - [launching] Support setting start levels in feature launching
Summary: [launching] Support setting start levels in feature launching
Status: VERIFIED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 4.13 M1   Edit
Assignee: Julian Honnen CLA
QA Contact:
URL:
Whiteboard:
Keywords: noteworthy
Depends on:
Blocks:
 
Reported: 2010-12-01 14:44 EST by Curtis Windatt CLA
Modified: 2019-06-26 04:55 EDT (History)
3 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 Curtis Windatt CLA 2010-12-01 14:44:17 EST 
While the feature based launching is intended to be as simple as possible, there is still a need to support setting start levels on a few specific plug-ins.

The user can add individual plug-ins to the launch.  We can add some options to set the start level at the bottom of the plug-in selection dialog.  This might not be perfect because of the multi selection property of the dialog.  The start level info (if different then default) would be listed in the table as part of the first column.

The feature wouldn't be immediately obvious, but would be available for the special cases that need it.
Comment 1 Curtis Windatt CLA 2010-12-01 14:46:01 EST 
Marking for 3.7, though there isn't anybody currently available to work on this.

There is also bug 328515 to improve feature launching in 3.7.
Comment 2 Eric Jain CLA 2011-03-10 19:40:29 EST 
I'd love to be able to use feature-based launches, because 1. our headless builds are product/feature-based (so we waste time keeping the launch configs in sync with the feature definitions), and moreover we develop on multiple platforms (unlike feature-based launches, plugin-based launches are platform-specific, so that's another set of files that needs to be kept in sync)...
Comment 3 Julian Honnen CLA 2019-06-11 08:06:27 EDT 
Plan for 4.13:

Add startlevel and autostart columns to the tree and make them editable for 'additional plugins'.
The value can be persisted in the existing additional_plugins property:

[plugin_id]:[version]:[resolution]:[checked]:[NEW startlevel]:[NEW autostart]
Comment 4 Eclipse Genie CLA 2019-06-17 10:24:43 EDT 
New Gerrit change created: https://git.eclipse.org/r/144267
Comment 5 Eclipse Genie CLA 2019-06-18 10:17:31 EDT 
New Gerrit change created: https://git.eclipse.org/r/144362
Comment 7 Eclipse Genie CLA 2019-06-19 03:00:18 EDT 
New Gerrit change created: https://git.eclipse.org/r/144405
Comment 10 Eclipse Genie CLA 2019-06-25 07:33:11 EDT 
New Gerrit change created: https://git.eclipse.org/r/144827
Comment 11 Eclipse Genie CLA 2019-06-25 09:07:57 EDT 
New Gerrit change created: https://git.eclipse.org/r/144839
Comment 14 Julian Honnen CLA 2019-06-26 04:55:20 EDT 
Verified on I20190625-1800