Hi,
Due to the recent slave additions on Hudson, I modified my build so that it starts by installing Buckminster using the p2 director (
from the Buckminster project), in order to obtain a Buckminster install that can run on each slave's architecture.
On slave5, the installation succeeds but Buckminster fails when I try to run it, with:
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
I have investigated the problem, and I noticed that on slave6, the buckminster/configuration/config.ini was not the same as on slave5 (I have attached the two files).
On slave6, it lists all the bundles, and there is no "org.eclipse.equinox.simpleconfigurator" directory.
I found this message that details this situation :
But I am not sure about what is causing this.
It may be because "org.eclipse.equinox.launcher" is missing its fragment :
On slave6, where it runs, I see the p2 director installed a fragment named "org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.100.v20110505"
On slave5, I would expect to see "org.eclipse.equinox.launcher.gtk.linux.ia64_*", but there is no such fragment.
I looked in the Eclipse update site :
find ~/downloads/eclipse/updates/3.7 -name 'org.eclipse.equinox.launcher.*'
And it lists all kinds of fragments, but the only one for ia64 is for hpux, not linux :
org.eclipse.equinox.launcher.gtk.hpux.ia64_32_1.0.0.v20110502.jar
Is the fragment needed? I would think not, since the director is an Eclipse product too, and it ran successfully.
But then what else could be missing?
I wish equinox would be a little more explanatory in its error message. I tried to run with "-debug" and "-consolelog", and I enabled tracing:
But it still doesn't give any clue (see attached log).
.: model driven agility :.