Community
Participate
Working Groups
I20090908-0800 When editing a PDE launch configuration setting the launch with option from "plugins selected below" to "all workspace + target plugins" should reset any changed start settings, since you can no longer edit the start levels, etc. Steps: 1. change the launch with setting of a config to "plugins selected..." and change a known bundle to autostart. Save configuration 2. launch to confirm it autostarts 3. edit the configuration to set the launch with setting back to the "all workspace..." option. Save configuration 4. relaunch and notice the bundle still auto-starts Expected: the bundle would no longer auto-start since I cannot change the setting when using the "all workspace..." launch with option.
Investigate in M3
as a point of interest, why is it that you cannot set the start settings when you choose All? Seems like the requirement to manage starting is separate from the need to choose bundles to be installed.
Didn't get to this in M3.
I couldn't reproduce using the steps you described, the bundles.info always has the default value. I also stepped through the code to see what could be going wrong. However, the code seems solid. When you use selected plug-ins below only, we save a list of checked plug-ins along with their start settings. When you switch back to 'all enabled', we don't clear the attributes (so when you switch the combo back your settings stay), but we do set another 'use default' attribute. There is only one method in the launcher where we access those custom start level settings and if the use default attribute is set, we never reach that code (using default:default). Closing as WORKSFORME since the code appears to be doing the right thing. Maybe in your case your default auto-start setting had been changed to true or maybe you were messing with the start level of a bundle that we have hard coded values for (ex. we set simple configurator's start level to a specific value if it is default).
