[eclipse-dev] change to config.ini syntax

[Jeff McAffer <Jeff_McAffer@xxxxxxxxxx>]

To enable several RCP and non-Update
scenarios we had to modify slightly the syntax used for the osgi.bundles
line in config.ini.  If you don't now what either of these are, you
can likely stop reading now as this only affects people who might be managing
their own values for osgi.bundles.

Previously you could list a set of bundles
to install and start using the syntax
osgi.bundles=org.eclipse.core.runtime@2,
org.eclipse.update.configurator@3

In config.ini (actually using any technique
for setting a System property).   This caused the listed plugins/bundles
to be discovered, installed and started with the given (optional) startlevel.
 Unfortunately there was no syntax for just installing a bundle without
starting it.  Given that we want, as usual, the default to be lazy
and not eagerly start plugins, the above syntax had to change.  

The new syntax which is equivalent to
the above is
#osgi.bundles=org.eclipse.core.runtime@2:start,
org.eclipse.update.configurator@3:start

Here the "start" attribute
is optional.  If it is not there then the bundle is just installed.
 It *may* be autostarted at a later time using the normla eclipse
autoactivation logic but it will not be eagerly started.

So what does this mean to you.  Well,
as mentioned above, nothing unless you actually know and care for an osgi.bundles
setting somewhere.  Existing configurations have this setting but
it is commented out (thus getting a default behaviour the runtime defines).
 If you do maintain an osgi.bundles property then you will have to
update its value when you try to run on the new code.  That code has
been released to HEAD and will show up in the nightlies as well as the
next integration build.

Jeff