|3.5M7 - Problem setting transform start levels [message #596755]
||Mon, 04 May 2009 18:29
Registered: July 2009
We build our _feature-based_ RCP product based on SDK headlessly as in |
We have transform plugins o.ee.eq.transforms.xslt.plugin and
o.e.eq.transforms.xslt and set the start level to @1:start explicitly in
config.ini,osgi.bundles after the build.
I really want to avoid editing config.ini, so looked forward to 3.5M7 and
support for setting start level in the Product file. I was encouraged to
see that in the Product editor, Configuration tab, I can now select the
transform plugins, an advance over 3.5M6. However, I can't actually edit
start level or autostart. The GUI just does not accept editing attempts.
Furthermore, if I enter the start level data directly into the Product
file, the Product fails to start with error: "IllegalStateException:
Unable to acquire application service. Ensure that the
org.eclipse.core.runtime bundle is resolved and started (see config.ini)".
What I see in config.ini for a successful 3.5M6 build (including my edits):
osgi.bundles=org.eclipse.equinox.transforms.xslt@1:start,org.eclipse.equinox.transforms.xslt.plugin@1:start,reference\:file\:org.eclipse.equinox.ds_1.1.0.v20090429-1630.jar@1\:start,reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.100.v20090429-212 6.jar @1\:start
In 3.5M7, with start level added to Product file and no longer making my
osgi.bundles=reference\:file\: org.eclipse.equinox.simpleconfigurator_1.0.100.v20090429-212 6.jar @1\:start
So, no transforms and o.e.eq.ds is gone!
What if anything, can I do to have PDE Build set transform start levels
Powered by FUDForum
. Page generated in 0.01658 seconds