Thanks, Thomas,
We did not use a custom config.ini, but looking into it, it turned out
that the config.ini from our original PDE-headless-build system
generated correctly using the configurator bundle, but the buckminster
generated config.ini just wouldn't work.
Is there some reason that the PDE build and buckminster don't generate
identical config.ini files?
This is buckminster for 3.4.
Again, many thanks.
Ki
Date: Fri, 19 Sep 2008 07:53:33 +0200
From: Thomas Hallgren <thomas@xxxxxxx <mailto:thomas@xxxxxxx>>
Subject: Re: [buckminster-dev] PDE headless build of RCP headless
product ... "The System Bundle's start level can not be
modified."
To: Buckminster developer discussions <buckminster-dev@xxxxxxxxxxx
<mailto:buckminster-dev@xxxxxxxxxxx>>
Message-ID: <48D33E5D.8050206@xxxxxxx <mailto:48D33E5D.8050206@xxxxxxx>>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Ki,
Do you have a custom config.ini file for you RCP app?
Are you using Buckminster for 3.3 or 3.4?
Regards,
Thomas Hallgren
Ki Alam wrote:
> Hi there.
>
> We are trying to transition our build from the PDE headless build to
> the buckminster headless build. We got through the resolve bits and
> are able to build , but when trying to run the build, we get the
> following error:
>
> !SESSION 2008-09-18 05:18:19.011
> ------------------------------
-----------------
> eclipse.buildId=unknown
> java.version=1.6.0_03
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>
> !ENTRY org.eclipse.osgi 4 0 2008-09-18 05:18:19.654
> !MESSAGE An unexpected runtime error has occurred.
> !STACK 0
> java.lang.IllegalArgumentException: The System Bundle's start level
> can not be modified.
> at
>
org.eclipse.osgi.framework.internal.core.StartLevelManager.setBundleStartLevel(StartLevelManager.java:415)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.installBundles(EclipseStarter.java:1117)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:642)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.access$1(EclipseStarter.java:619)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter$1.bundleChanged(EclipseStarter.java:308)
> at
>
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1234)
> at
>
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
> at
>
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework.java:1518)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1469)
> at
>
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:281)
> at
>
org.eclipse.osgi.framework.internal.core.StartLevelManager.launch(StartLevelManager.java:247)
> at
>
org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:201)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:644)
> at
> org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:313)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597) at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
> at
> org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at
> org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>
> !ENTRY org.eclipse.osgi 4 0 2008-09-18 05:18:19.655
> !MESSAGE
> !STACK 0
> java.lang.IllegalArgumentException: The System Bundle's start level
> can not be modified.
> at
>
org.eclipse.osgi.framework.internal.core.StartLevelManager.setBundleStartLevel(StartLevelManager.java:415)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.installBundles(EclipseStarter.java:1117)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:642)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.access$1(EclipseStarter.java:619)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter$1.bundleChanged(EclipseStarter.java:308)
> at
>
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:1234)
> at
>
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
> at
>
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:141)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework.java:1518)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1469)
> at
>
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:281)
> at
>
org.eclipse.osgi.framework.internal.core.StartLevelManager.launch(StartLevelManager.java:247)
> at
>
org.eclipse.osgi.framework.internal.core.SystemBundle.resume(SystemBundle.java:201)
> at
>
org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:644)
> at
> org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.java:51)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:313)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:175)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597) at
> org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
> at
> org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at
> org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
>
> !ENTRY org.eclipse.osgi 4 0 2008-09-18 05:18:19.656
> !MESSAGE Application error
> !STACK 1
> java.lang.IllegalStateException: Platform not running
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:370)
> at
>
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
>
> Followed by the bundles not being able to be resolved:
>
>
> !ENTRY org.eclipse.osgi 2 0 2008-09-18 05:18:19.677
> !MESSAGE One or more bundles are not resolved because the following
> root constraints are not resolved:
> !SUBENTRY 1 org.eclipse.osgi 2 0 2008-09-18 05:18:19.677
> !MESSAGE Bundle
> initial@reference:file:plugins/m365.agent.logmessageservice_1.0.0.jar/
> was not resolved.
> !SUBENTRY 2 m365.agent.logmessageservice 2 0 2008-09-18 05:18:19.678
> !MESSAGE Missing required bundle wily.introscope.em_0.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2008-09-18 05:18:19.678
> !MESSAGE Bundle
>
initial@reference:file:plugins/m365.embeddedem.datacenter.properties_1.0.0.jar/
> was not resolved.
> !SUBENTRY 2 m365.embeddedem.datacenter.properties 2 0 2008-09-18
> 05:18:19.678
> !MESSAGE Missing host wily.introscope.em_1.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2008-09-18 05:18:19.678
> !MESSAGE Bundle
>
initial@reference:file:plugins/m365.messaging.transport.sender_1.0.0.jar/
> was not resolved.
> !SUBENTRY 2 m365.messaging.transport.sender 2 0 2008-09-18 05:18:19.678
> !MESSAGE Missing imported package m365_0.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2008-09-18 05:18:19.678
> !MESSAGE Bundle
>
initial@reference:file:plugins/m365.agent.classanalysis.isengard_1.0.0.jar/
> was not resolved.
> !SUBENTRY 2 m365.agent.classanalysis.isengard 2 0 2008-09-18
05:18:19.678
> !MESSAGE Missing required bundle wily.introscope.em_0.0.0.
> !SUBENTRY 1 org.eclipse.osgi 2 0 2008-09-18 05:18:19.678
> !MESSAGE Bundle
> initial@reference:file:plugins/m365.isengard_1.0.0.jar/ was not
resolved.
> !SUBENTRY 2 m365.isengard 2 0 2008-09-18 05:18:19.678
> !MESSAGE Missing required bundle wily.introscope.em_0.0.0.
>
> We are able to build using the existing PDE-headless build ... has
> anyone run into this?
>
> Thanks,
> Ki
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@xxxxxxxxxxx <mailto:buckminster-dev@xxxxxxxxxxx>
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
------------------------------------------------------------------------
_______________________________________________
buckminster-dev mailing list
buckminster-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/buckminster-dev