Grails / Groovy / GGTS: Conflicting module versions on run-app

Question

After upgrading a Grails application from 2.2.0 to 2.2.1 I keep getting the following error when attempting to debug a Grails application from GGTS via Debug as... -> Grails

Answer 1

Another solution worked for me when Eclipse stopped being able to run my project with the "groovy-all is loaded in version ... and you are trying to load version" error.

Manually removing a groovy-all line from the .classpath fixed it.

<classpathentry kind="lib" path="Libraries/groovy-all-2.1.2.jar"/>

I found the solution in this blog post.

Answer 2

I had the same exception, when I was trying to run JUnit tests on my Spring boot project in Eclipse only, mvn executes them fine. I'm not using Gradle or Groovy. Indeed checking the test's class path upon debug, showed two versions of groovy.jar. The work version of the groovy.jar was picked from other projects in the Eclipse workspace. I was able to fix it by removing Resolve dependencies from Workspace projects in project properties -> Maven

Answer 3

I had the same problem and i solved it by:

1. For your project: Open Run As->Run Configurations
2. Go to the Refresh tab
3. Check the Refresh resources upon completion
4. Press Run

That did the trick for me.

Answer 4

I have no explanation why it didn't work, but I found a workaround.

I had another run target configured for the same app, but with a -Dgrails.env=... setting, which I could launch without problems. I simply copied this config and removed the parameter. That way, I basically recreated the simple launch config which previously kept failing.

Problem gone.