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

When I change the grails project's name it works correctly.

Answer 2

I solved it by removing the option to manually load the classpath in Run Configuration. It was using the wrong Grails version (2.5.0 instead of 2.5.1).

Basically the wrong classpath was used.

Maybe this brings someone on the correct path :)

Answer 3

i had this problem on Grails 2.2.0 on Ubuntu machine , i fixed it with the below steps :

1. open eclipse go to "Run as" the "Run Configurations"
2. choose "Environment" tab , then choose "replace native environment with specified environment "

that solved the problem for me .. hope this help

Answer 4

I deleted .metadata in GGTS workspace and reimport project. It works, I can run-app again.

Answer 5

I know this is a GGTS question, but Google led me here and this seems to be a common issue even after several years so I'm posting this answer here. Hopefully it can help other STS users who also land here.

I had this problem with Spring Tool Suite, using Spring Boot Version 1.3.3.RELEASE and gradle version 2.14. There is some internal dependency on groovy 2.4.6 and groovy-all 2.4.6, but my Eclipse workspace Groovy Libraries are version 2.4.7. Removing the Groovy Libraries from the Spring/Gradle project properties(s) works for running those projects, but for other Groovy projects in the workspace you are stuck between a rock and a hard place. They will either run if you click yes when "Errors exist in project. Run anyway?" if you remove the Groovy libs from the properties build path, or they will not have project errors if you put the Groovy libs in the properties build path.

Resolved by adding explicit dependencies in build.gradle on groovy 2.4.7 and groovy-all 2.4.7 for Gradle projects in the workspace

compile('org.codehaus.groovy:groovy:2.4.7')
compile('org.codehaus.groovy:groovy-all:2.4.7')

and (close Eclipse STS) then removing the 2.4.6 folder(s) from the .gradle cache

<path to>\.gradle\caches\modules-2\files-2.1\org.codehaus.groovy\groovy\2.4.6
<path to>\.gradle\caches\modules-2\files-2.1\org.codehaus.groovy\groovy-all\2.4.6

and (Open STS) then right-click gradle project(s)>gradle>refresh gradle project

Now other Groovy projects in the workspace run without the 2.4.6 vs 2.4.7 conflict.

Answer 6

Manually delete the run-app Run Configuration so it gets recreated. This was reported as a bug on Aug. 1st, 2013. Bug report: https://issuetracker.springsource.com/browse/STS-3501