| Re: [eclipse-dev] change to config.ini syntax - PLEASE READ |
>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.
Jeff's note actually should have an appeal to a wider audience, as it will
present yet another breaking point in the self-hosting story. Here is
why...
Starting from the first I-build that supports the new config.ini syntax,
you will not be able to use a relatively older I-build (e.g. last week's I-
build and earlier) as your target platform.
This is because PDE now uses this new syntax to generate the config.ini
which we pass to the runtime workbench. This new syntax(e.g. @2:start)
will not be understood by the older target platform, and it will choke upon
startup. So backward compatibility with ALL previous 3.0 builds will now
be broken.
Also, as you would expect, forward compatiblity is not going to work
either. That is, you can't use an older (e.g. last week's I-build or
earlier) platform as your host and then target this week's I-build.
This is because the host platform will generate a config.ini of the old
syntax, which, when passed to the (newer) target platform will indeed be
understood. However, it will not contain the ":start" portions, so
org.eclipse.update.configurator will not get automatically started and the
runtime workbench will not start.
As long as your host platform === target platform, you should be OK.
As always, 2.x backward compatiblity is/was/always will be supported and is
not affected by this change.
Wassim Melhem
(Embedded image moved to file: pic30172.gif) Wassim Melhem
Staff Software Developer, The Eclipse Project
IBM Toronto Laboratory
8200 Warden Ave, Markham, ON L6G 1C7
Internal Mail: D2/R0Q/8200/MKM PWA: 343
Phone: 905-413-2620 T/L: 969-2620 Fax: 905-413-4854
email: wassimm@xxxxxxxxxx
Jeff
McAffer/Ottawa/IB
M@IBMCA To
Sent by: eclipse-dev@xxxxxxxxxxx
eclipse-dev-admin cc
@eclipse.org
Subject
[eclipse-dev] change to config.ini
05/07/2004 05:09 syntax
PM
Please respond to
eclipse-dev
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.
JeffAttachment:
pic30172.gif
Description: GIF image
