STS 3.0.0.M1 released

[bobgutierrez]

STS 3.0.0 M1 on MacOSX Cocoax64 with Eclipse 4.2 was working all well until some updates showed up. After installing them without any problem, STS never started again.

Here is the trace log.

Screen Shot 2012-06-06 at 11.45.09 AM.jpg

Code:

!SESSION 2012-06-06 11:44:18.044 -----------------------------------------------
eclipse.buildId=3.0.0.201205010613-M1-e42
java.version=1.6.0_31
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments:  -product com.springsource.sts.ide -keyring /Users/xxxxxxxx/.eclipse_keyring -showlocation
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product com.springsource.sts.ide -keyring /Users/xxxxxxxx/.eclipse_keyring -showlocation

!ENTRY org.eclipse.osgi 4 0 2012-06-06 11:44:19.083
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
	at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:225)
	at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:657)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:274)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
	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:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
Caused by: java.lang.IllegalStateException: Expected to find an object at table index: 1045
	at org.eclipse.osgi.internal.resolver.StateReader.getFromObjectTable(StateReader.java:81)
	at org.eclipse.osgi.internal.resolver.StateReader.readExportPackageDesc(StateReader.java:411)
	at org.eclipse.osgi.internal.resolver.StateReader.readExportPackageDesc(StateReader.java:420)
	at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:297)
	at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:809)
	at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.loadLazyData(BundleDescriptionImpl.java:662)
	at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getExportPackages(BundleDescriptionImpl.java:160)
	at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.setFrameworkVersion(PackageAdminImpl.java:708)
	at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.setResolvedBundles(PackageAdminImpl.java:658)
	at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:67)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
	... 12 more
Root exception:
java.lang.IllegalStateException: Expected to find an object at table index: 1045
	at org.eclipse.osgi.internal.resolver.StateReader.getFromObjectTable(StateReader.java:81)
	at org.eclipse.osgi.internal.resolver.StateReader.readExportPackageDesc(StateReader.java:411)
	at org.eclipse.osgi.internal.resolver.StateReader.readExportPackageDesc(StateReader.java:420)
	at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:297)
	at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:809)
	at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.loadLazyData(BundleDescriptionImpl.java:662)
	at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getExportPackages(BundleDescriptionImpl.java:160)
	at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.setFrameworkVersion(PackageAdminImpl.java:708)
	at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.setResolvedBundles(PackageAdminImpl.java:658)
	at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:67)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
	at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:225)
	at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:657)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:274)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
	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:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

!ENTRY org.eclipse.osgi 4 0 2012-06-06 11:44:19.084
!MESSAGE Startup error
!STACK 1
java.lang.RuntimeException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
	at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:233)
	at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:657)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:274)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
	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:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
	at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:225)
	... 10 more
Caused by: java.lang.IllegalStateException: Expected to find an object at table index: 1045
	at org.eclipse.osgi.internal.resolver.StateReader.getFromObjectTable(StateReader.java:81)
	at org.eclipse.osgi.internal.resolver.StateReader.readExportPackageDesc(StateReader.java:411)
	at org.eclipse.osgi.internal.resolver.StateReader.readExportPackageDesc(StateReader.java:420)
	at org.eclipse.osgi.internal.resolver.StateReader.readBundleDescriptionLazyData(StateReader.java:297)
	at org.eclipse.osgi.internal.resolver.StateReader.fullyLoad(StateReader.java:809)
	at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.loadLazyData(BundleDescriptionImpl.java:662)
	at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getExportPackages(BundleDescriptionImpl.java:160)
	at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.setFrameworkVersion(PackageAdminImpl.java:708)
	at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.setResolvedBundles(PackageAdminImpl.java:658)
	at org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start(SystemBundleActivator.java:67)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
	... 12 more

[Martin Lippert]

Hey!

It looks like your M1 installation got corrupted by the update. As mentioned in the post before, there seems to be a problem with the update site and silent updates of the Eclipse platform itself when you update and/or install some unrelated things. I would recommend to use M1 without updating anything or wait for M2 (should be available next week), that should have a more stable update site.

HTH,
Martin

[GordonRehling]

Martin,

I've still got my old STS 2.9 so will go back to that. Guess I should keep a look out for 3.0.0.M2 ;-)

Gordon

[bobgutierrez]

I installed STS 3.0.0.M1 Cocoa x64 but this time with Eclipse 3.7 and worked flawless. I guess the trouble is with Eclipse 4.2.

[PDSB_Greg]

This is likely more of an Eclipse question...Is there a way to get rid of the coloring on the toolbars? The light blue fades look silly and are distracting against the rest of the grey background.

[bobgutierrez]

STS 3.0.0.M1 w/Eclipse 4.2 after installed on OSX latest Java, asks for some updates, this updates causes that when restarting failed the startup. On the other hand, STS 3.0.0.M1 w/Eclispe 3.7 runs flawless without any trouble after updates.

As time passes Eclipse 3.7 will be outdated and 4.x will be there. So, it is not about colors or toolbars, it is about some modules making conflict.

Error w/Eclipse 4.2

!SESSION 2012-06-06 11:44:18.044 -----------------------------------------------
eclipse.buildId=3.0.0.201205010613-M1-e42
java.version=1.6.0_31
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments:  -product com.springsource.sts.ide -keyring /Users/xxxxxxxx/.eclipse_keyring -showlocation
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product com.springsource.sts.ide -keyring /Users/xxxxxxxx/.eclipse_keyring -showlocation

!ENTRY org.eclipse.osgi 4 0 2012-06-06 11:44:19.083
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.osgi.framework.internal.core.SystemBundleActivator.start() of bundle org.eclipse.osgi.
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
	at org.eclipse.osgi.framework.internal.core.InternalSystemBundle.resume(InternalSystemBundle.java:225)
	at org.eclipse.osgi.framework.internal.core.Framework.launch(Framework.java:657)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:274)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
	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:629)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
Caused by: java.lang.IllegalStateException: Expected to find an object at table index: 1045

[PDSB_Greg]

Found my answer. It's controlled by CSS and can be changed in the preferences.

[Martin Lippert]

Hey!

STS 3.0.0.M1 w/Eclipse 4.2 after installed on OSX latest Java, asks for some updates, this updates causes that when restarting failed the startup. On the other hand, STS 3.0.0.M1 w/Eclispe 3.7 runs flawless without any trouble after updates.

As time passes Eclipse 3.7 will be outdated and 4.x will be there. So, it is not about colors or toolbars, it is about some modules making conflict.

There seemed be to some problems with M1 after installing updates or additional plugins. Meanwhile we have an (not yet announced) M2 build for 3.0.0 out there (from the usual download pages). Can you try your setting with that build? It should work a lot better now.

HTH,
Martin

[peterox]

I'm having the same problem on M2. See attached log

If I run using the -clean argument it starts up

[Martin Lippert]

Hey!

Thanks for the log file. This seems to be related to a problem in the underlying Equinox runtime. Does it help to startup with the -clean option once? Or do you need to start STS with -clean every time?

-Martin