Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Changes to config.ini in 3.1M7 breaks my build
Changes to config.ini in 3.1M7 breaks my build [message #285778] Wed, 25 May 2005 13:36
Eclipse UserFriend
Originally posted by: mark_melvin.amis.com

Hi there,

I just tried to rebuild my product based on 3.1M7 (well - yesterday's
nightly build actually), and I found it would not start. It kept
crashing with the following exception:

!ENTRY org.eclipse.osgi 2005-05-25 13:25:47.425
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service.
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:363)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:161)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:330 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:274)
at org.eclipse.core.launcher.Main.run(Main.java:969)
at org.eclipse.core.launcher.Main.main(Main.java:944)

After a bunch of head-beating, I noticed a difference in the old
config.ini I was using and the one in last night's build - in particular
this line is now uncommented:

osgi.bundles=org.eclipse.core.runtime@2:start,
org.eclipse.update.configurator@3:start

Is this line now a requirement for eclipse to run, and what the heck
does it do?

Thanks,
Mark.
Previous Topic:How to access AntCorePreferences programatically
Next Topic:Editor Action Contributors
Goto Forum:
  


Current Time: Mon Jun 16 12:08:16 EDT 2025

Powered by FUDForum. Page generated in 0.03475 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top