I’m struggling to get Buckminster to produce an
Eclipse product. My ideal end result is a package with the appropriate
features, plugins, config.ini, and launcher. The attached set of projects
produce a very nice Eclipse export (complete with the JRE!). However, I
am unable to get Buckminster to produce a correct product. The only
difference I see between the two builds is the configuration directory,
particularly the config.ini file.
The Eclipse exported config.ini is:
#Product Runtime
Configuration File
osgi.splashPath=platform:/base/plugins/learn.buckminster.headless
eclipse.product=learn.buckminster.headless.headlessproduct
osgi.bundles.defaultStartLevel=4
osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
The Buckminster config.ini is:
#Product Runtime
Configuration File
eclipse.product=learn.buckminster.headless.headlessproduct
osgi.bundles=org.eclipse.core.contenttype,org.eclipse.core.jobs,org.eclipse.core.runtime.compatibility.auth,org.eclipse.core.runtime.compatibility,org.eclipse.core.runtime,org.eclipse.equinox.app@start,org.eclipse.equinox.common@start:2,org.eclipse.equinox.preferences,org.eclipse.equinox.registry,org.eclipse.osgi,org.eclipse.update.configurator,learn.buckminster.headless,org.eclipse.equinox.launcher.win32.win32.x86,org.eclipse.equinox.launcher
osgi.bundles.defaultStartLevel=4
I don’t want to maintain config.ini files manually
and, ideally, the config would list each bundle individually as Buckminster
does.
What am I missing?