Community
Participate
Working Groups
Currently PDE build hard-codes start levels and autoStart settings for certain well known bundles. We need a way to externalize those default start levels, etc, to make the build more flexible. In bug 255718 it was suggested we do this in the publisher, but I'd like to see if there are other options.
Some options: 1) we never generate defaults, and if someone creates a product that doesn't specify the start level for equinox.common, etc, it will fail 2) The product editor in PDE UI inserts some defaults when the user adds platform features or bundles to a product 3) We bump up the version number of the .product, and only automatically insert default values for old product versions. New .product files created today would have new version with implicit defaults (perhaps product editor would add some) 4) We hard-code defaults in the publisher
Option number 5 would be what was discussed at the Equinox call and summarized here: http://wiki.eclipse.org/Equinox/p2/GeneratingCUs That is, creating "configure" features.
*** Bug 240715 has been marked as a duplicate of this bug. ***
consider later
Moving to inbox
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.
