When you generate the metadata for the SDK, do you have all the plug-ins of
the SDK available?
Also do you have a config.ini and an eclipse.ini when you generate?
I tried to respond via the web gateway earlier today, but that message
apparently hasn't gone through yet. If it winds up here later, I
apologize for the duplication.
I started with compiling the source build for the Eclipse 3.4 SDK. I
had to modify the build scripts for the launcher and SWT, since this
isn't a supported platform, but once I was finished, Eclipse would
start. I then noticed that the p2 update manager wasn't working, so
checked on the config. My build was using
org.eclipse.update.configurator, rather than the new
equinox.simpleconfigurator, and I had no p2 data.
I then used the generator app, which gave me the artifacts.jar and
content.jar which listed all 300+ bundles in my SDK source build. I
then used the generator app to install these bundles into a new
location. The new location did have an eclipse.ini, config.ini and a
proper p2 directory with a profile, but config.ini was still referencing
org.eclipse.update.configurator. Also, this build wouldn't run (I
didn't think to check whether it included the update.configurator
bundle, but that's not what I want anyway).
I found that I need the bundles.info file for the simpleconfigurator to
work, and I found the code in simpleconfigurator.manipulator which
writes that data out to file, but I'm not sure how to trigger that from
the director application. By mucking at the OSGi console for the
director application, I can see that it is loading
simpleconfigurator.manipulator, but none of the services from that
bundle are being referenced. I'm assuming that I'm missing some
configuration flag which tells it to translate the info from the
original config.ini osgi.bundles property into the new bundles.info
file, but perhaps this is something that has to be bootstrapped manually.