Spring Tool Suite
  1. Spring Tool Suite
  2. STS-2587

STS can't find method in latest snapshot: CompilerUtils.getGroovyVersion()

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Critical Critical
    • Resolution: Complete
    • Affects Version/s: 3.0.0.RELEASE
    • Fix Version/s: 3.0.0.M1
    • Component/s: EDITING, GRAILS, UI
    • Labels:
      None
    • Environment:

      Windows 7 Home premium.
      JDK 6u30.
      Grails 1.3.7 and 2.0.3 (error with projects configured for both versions)
      Groovy plugin for eclipse
      SpringSource Tool Suite 3.0.0.201204180739-SNAPSHOT

      Description

      I don't how this has come up. I've been using STS since pretty more than 3 months for now. But today when I exited the workbench & returned back & started STS, it comes up with a series of errors (failing for nearly all usual operations: Initializing Java Tooling, Refreshing DSLD Scripts etc, Add DSL Support, Updating project dependencies, Compute launch button tooltip...) all due to only one reason:

      An internal error occurred during: "<operation>"
      org.codehaus.groovy.eclipse.core.compiler.CompilerUtils.getGroovyVersion()Ljava/lang/String;

      Sometimes same error is repeated with little different message:

      An error has occurred. See error log for more details.
      org.codehaus.groovy.eclipse.core.compiler.CompilerUtils.getGroovyVersion()Ljava/lang/String;

      This happens whenever I open any Grails project or start STS with a Grails project open.

      This is the error I see in the .log file:

      !SESSION 2012-04-20 17:34:59.402 -----------------------------------------------
      eclipse.buildId=2.9.1.201203221000-RELEASE
      java.version=1.6.0_27
      java.vendor=Sun Microsystems Inc.
      BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_IN
      Framework arguments: -product com.springsource.sts.ide
      Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.springsource.sts.ide

      This is a continuation of log file E:\Eclipse Workspaces\TPI\.metadata\.bak_7.log
      Created Time: 2012-04-20 17:38:06.293

      !ENTRY org.eclipse.ui.navigator 4 2 2012-04-20 17:38:06.293
      !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.navigator".
      !STACK 0
      java.lang.NoSuchMethodError: org.codehaus.groovy.eclipse.core.compiler.CompilerUtils.getGroovyVersion()Ljava/lang/String;
      at com.springsource.sts.grails.commands.GroovyCompilerVersionCheck.check(GroovyCompilerVersionCheck.java:97)
      at com.springsource.sts.grails.core.internal.classpath.GrailsClasspathContainerInitializer.initialize(GrailsClasspathContainerInitializer.java:28)
      at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2848)
      at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1877)
      at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2811)
      at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2695)
      at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2859)
      at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1964)
      at org.eclipse.jdt.internal.core.JavaModelManager.determineIfOnClasspath(JavaModelManager.java:1011)
      at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:897)
      at org.eclipse.jdt.internal.core.JavaModelManager.create(JavaModelManager.java:838)
      at org.eclipse.jdt.core.JavaCore.create(JavaCore.java:2696)
      at org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider.convertToJavaElements(JavaNavigatorContentProvider.java:255)
      at org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider.interceptRefresh(JavaNavigatorContentProvider.java:314)
      at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.interceptRefresh(SafeDelegateTreeContentProvider.java:247)
      at org.eclipse.ui.internal.navigator.NavigatorPipelineService$3.run(NavigatorPipelineService.java:188)
      at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
      at org.eclipse.ui.internal.navigator.NavigatorPipelineService.pipelineInterceptRefresh(NavigatorPipelineService.java:184)
      at org.eclipse.ui.internal.navigator.NavigatorPipelineService.interceptRefresh(NavigatorPipelineService.java:167)
      at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:342)
      at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:510)
      at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider$3.run(ResourceExtensionContentProvider.java:294)
      at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider.runUpdates(ResourceExtensionContentProvider.java:306)
      at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider.access$1(ResourceExtensionContentProvider.java:303)
      at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider$1.run(ResourceExtensionContentProvider.java:129)
      at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
      at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
      at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
      at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
      at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
      at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
      at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
      at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
      at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
      at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
      at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
      at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      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:622)
      at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
      at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
      at org.eclipse.equinox.launcher.Main.main(Main.java:1386)

      ...

      and then the same is repeated for nearly all the plugins used by the projects.

      I reinstalled the whole Groovy Compiler but no luck! I take STS updates almost daily. Can you guys please look into this? All of my work is hanged because of this!
      – Configuration Details –
      Product: SpringSource Tool Suite 3.0.0.201204180739-SNAPSHOT (com.springsource.sts.ide)
      Installed Features:
      com.springsource.sts 3.0.0.201204180739-SNAPSHOT

      1. .log
        501 kB
        Vishwajeet Pandey

        Activity

        Hide
        Vishwajeet Pandey added a comment -

        I've managed to get going with a latest milestone (had to reinstall & update to latest milestone) for now. Hope this issue will still help you figure out for future snapshot developments.

        Show
        Vishwajeet Pandey added a comment - I've managed to get going with a latest milestone (had to reinstall & update to latest milestone) for now. Hope this issue will still help you figure out for future snapshot developments.
        Hide
        Andy Clement (c) added a comment -

        Good catch! Thanks for the clear bug report. This was due to a change in greclipse snapshots to start supporting Groovy 2.0. I've re-added a compatible version of the method for use by Grails. Following nightly snapshots of STS is a bit on the bleeding edge - but they ought to work.

        Show
        Andy Clement (c) added a comment - Good catch! Thanks for the clear bug report. This was due to a change in greclipse snapshots to start supporting Groovy 2.0. I've re-added a compatible version of the method for use by Grails. Following nightly snapshots of STS is a bit on the bleeding edge - but they ought to work.
        Hide
        Andy Clement (c) added a comment -

        should be addressed in the next few hours when a new groovy snapshot comes through.

        Show
        Andy Clement (c) added a comment - should be addressed in the next few hours when a new groovy snapshot comes through.
        Hide
        Vishwajeet Pandey added a comment -

        Thanks very much! I'll again start updating to nightly builds then. I've better thought to keep two STS installations now: one subscribed to only milestone & release builds and other to nightly builds as well.

        Show
        Vishwajeet Pandey added a comment - Thanks very much! I'll again start updating to nightly builds then. I've better thought to keep two STS installations now: one subscribed to only milestone & release builds and other to nightly builds as well.
        Hide
        Mirko Raner added a comment -

        Same problem here. A quick resolution of this issue is appreciated!

        Show
        Mirko Raner added a comment - Same problem here. A quick resolution of this issue is appreciated!
        Hide
        Andy Clement (c) added a comment -

        This was fixed on friday but the groovy-eclipse build is proving unstable - (intermittent test failures) - I'll keep kicking it until a build goes through.

        Show
        Andy Clement (c) added a comment - This was fixed on friday but the groovy-eclipse build is proving unstable - (intermittent test failures) - I'll keep kicking it until a build goes through.
        Hide
        Andy Clement (c) added a comment -

        snapshot build is through now - this should be fixed.

        Show
        Andy Clement (c) added a comment - snapshot build is through now - this should be fixed.

          People

          • Assignee:
            Andy Clement (c)
            Reporter:
            Vishwajeet Pandey
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              First Response Date: