Groovy version conflicts when running farmStart with a war file.

[rszewczyk]

I'm using gretty (v1.1.3) with a war file from a Grails application that uses groovy 2.1.9. The application fails to start when running farmStart with the error: groovy-all is loaded in version 2.1.9 and you are trying to load version 2.3.6. My current workaround is to delete the groovy-all jar from the exploded war file. Is there a way to have Gretty not put its version of groovy on the classpath when using a war file?

[akhikhl]

It's difficult to remove groovy from webapps classpath, because webapp must get parent classloader from server, otherwise Servlet API would not work.
I faced a similar problem in September and settled for a different solution: forcibly upgrade groovy version in the webapp to the one used in the server.
Could you, please, try whether my solution would work for you? You'll need to apply Gretty 1.1.4-SNAPSHOT:

buildscript {
  repositories {
    // ...
    maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
  }
  dependencies {
    classpath 'org.akhikhl.gretty:gretty:1.1.4-SNAPSHOT'
  }
}

apply plugin: 'org.akhikhl.gretty'

repositories {
  // ...
  maven { url 'http://oss.jfrog.org/artifactory/oss-snapshot-local' }
}

[rszewczyk]

Yes - it works. It seems a little bit backwards to force the webapp to use a different version of groovy - however for my current use case (a convenient way to run functional tests) it should be fine.

Thank you for the quick reply. This is a really great plugin.

[akhikhl]

I'll meditate on classpath riddle and maybe I'll find a solution with better isolation between server and webapp.
The release 1.1.4 is coming today late evening or tomorrow morning. I'm currently documenting a lot of new features and fixes 😄

[akhikhl]

Gretty release 1.1.4 is out, with abovementioned groovy version fix. Please use it instead of snapshot.

[akhikhl]

I just fixed related bug on Gretty 1.1.5-SNAPSHOT:
There's groovy version conflict, when running spring-boot product with groovy version different from 2.3.7.
I hope I "covered all bases" regarding groovy version conflict. Now it should be back to "just works" mode.

[akhikhl]

@rszewczyk , can you confirm that the problem is solved in 1.1.4?

[rszewczyk]

Sorry for the delayed response. Yes - it works in the 1.1.4 release. Thanks!