Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321338 - PDE product configurations should support the same start-level/auto-start settings as a PDE launch configuration
Summary: PDE product configurations should support the same start-level/auto-start set...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-30 09:20 EDT by Christian Kesselheim CLA
Modified: 2019-11-27 07:19 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 Christian Kesselheim CLA 2010-07-30 09:20:12 EDT 
Build Identifier: 

It would certainly feel more consistent if PDE would allow to configure the same set of start-level/auto-start default levels at the product level as it does for any of its launch configurations.

Especially the ability to define an auto-start default value would come in handy, since there is currently (to my knowledge) no corresponding Equinox property available that would allow to globally set the auto-start setting without re-enumerating all of the to-be-provisioned bundles.

Reproducible: Always
Comment 1 Curtis Windatt CLA 2010-08-03 10:14:41 EDT 
Moving to UI.  No plans to work on this.
Comment 2 Lars Vogel CLA 2019-11-27 07:19:11 EST 
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.