Skip to Content

<buildProduct> created config.ini differs from the PDE created one

Posted in

Hello,

when doing a product export via ant4eclipse the created config.ini doesn't respect the org.eclipse.equinox.simpleconfigurator plugin if this is present in target platform, ending up that the created config.ini doesn't have the necessary settings for org.eclipse.equinox.simpleconfigurator. As far as i know, using the SimpleConfigurator-Plugin results in a separate bundles.info file, which holds all information of the necessary bundles - see http://wiki.eclipse.org/Configurator#SimpleConfigurator.

The PDE export produces these config.ini:

#Wed Dec 15 13:10:27 CET 2010
eclipse.buildId=Version 2.0.6 GA (b180)
osgi.bundles=org.eclipse.equinox.simpleconfigurator@1\:start
eclipse.application=com.xyz.application
osgi.bundles.defaultStartLevel=4
eclipse.product=com.xyz.desktop
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.eclipse.equinox.simpleconfigurator/bundles.info
osgi.splashPath=platform\:/base/plugins/com.xyz.application

but ant4eclipse produces these config.ini:

#Product Runtime Configuration File
eclipse.application=com.xyz.application
eclipse.product=com.xyz.application
osgi.bundles.defaultStartLevel=4
osgi.bundles=<....very long list of all plugins used in this product....>

Workaround

Hi Rhodan,

I have to take a closer look at it...

As a workaround you can specify to use an existing 'config.ini' file in your product.xml file (Configuration-Tab).

Regards,
Gerd

I will give it a try.

I will give it a try. Ironically "Using an exisiting config.ini" is currently a bug in original PDE-Export, which doesn't honour these option, but possibly ant4eclipse can do it.

I noticed too, that the

I noticed too, that the created config.ini also references the wrong "eclipse.product"-property - it should be com.xyz.desktop as by PDE.