Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 270366 - Startlevel settings of plugins in run configuration are ignored
Summary: Startlevel settings of plugins in run configuration are ignored
Status: RESOLVED DUPLICATE of bug 269111
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5   Edit
Hardware: All Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-28 21:27 EDT by Philipp Kursawe CLA
Modified: 2009-03-29 21:34 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Kursawe CLA 2009-03-28 21:27:09 EDT
Build id: I20090317-1745
In my build all the start settings I set for plugins of my Eclipse Application run config are ignored (not put into the dynamically created config.ini).
If I set a plugins startlevel to 2 and autostart = true it is still only resolved, not started and a "sl <bundleid>" of this bundle reveals that is still has the default start level of 4. Even configuration are clean and workspace cleaning does not help.

Not sure if that is Platform UI/debug or PDE?
Comment 1 Philipp Kursawe CLA 2009-03-28 21:38:20 EDT
This can be solved by adding the simpleconfigurator to the run config as suggested in #269111. 

Does this mean the bundle startlevel is configured at runtime when simpleconfigurator is started? Or does PDE check for simpleconfigrator and uses it to generate the config.ini? I am confused. I thought what I enter in the run config dialog is written to the config.ini
Comment 2 Philipp Kursawe CLA 2009-03-28 21:40:20 EDT
changed to PDE/UI
Comment 3 Chris Aniszczyk CLA 2009-03-29 21:33:27 EDT
If simpleconfigurator is used, we write out a bundles.info that is used by simpleconfigurator and that has bundle start level info in it. Not your config.ini :)
Comment 4 Chris Aniszczyk CLA 2009-03-29 21:34:41 EDT

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