Announcement Announcement Module
No announcement yet.
STS 2.3.2 Groovy editing broken after version change Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • STS 2.3.2 Groovy editing broken after version change


    I've been using STS 2.3.2 to do some Grails development with deployment to Cloud Foundry. My first deployment attempt failed with an error message saying it couldn't find the class definition for org.groovy.transform.powerassert.ValueRecorder. A web search indicated this was due to using Groovy 1.7.1.

    I changed the project settings to use Groovy 1.6.0. This restarted STS and I was able to recompile, re-war, upload, and deploy, but thereafter my STS wouldn't allow me to edit any Groovy file -- double clicking a Groovy file results in a dialog popping up with the error message
    "An error has occurred.
    org.codehaus.groovy.ast.ModuleNode.getStaticImport s()Ljava/util/Map;"

    I'd appreciate any suggestions on how to solve this.



  • #2
    Hi Peter,

    We are aware of some problems with 1.6 support in Groovy-Eclipse. Please see:

    We have just released a new snapshot version of Groovy-Eclipse that should address your problems. Please use the following update site:

    Also, please get back to us if this fixes things (or, of course, if it doesn't).


    • #3
      Thanks for the reply Andrew.

      I did a normal Help -> Check for Updates which revealed at least 10 updates, including the Groovy-Eclipse Feature, so I applied them and that did the trick. I picked it up with the pre-existing update site:



      • #4
        I wasn't aware that you were running on 3.5. I'm not sure if the changes have been backported to the 3.5 stream yet.


        • #5
          I had originally installed STS 2.3.1 and then upgraded it to 2.3.2. That was the version I was running when the problem arose.


          • #6
            OK. So please let me know if you continue to have any problems. I'll be doing a refresh of the 3.5 stream of Groovy-Eclipse next week and I can make sure that everything works for you.