Monday, 11 May 2015

Groovy Eclipse compiler versions and ShortTypeHandling

Just a short note to remind myself.

If you come across a classNotFoundException: org.codehaus.groovy.runtime.typehandling.ShortTypeHandling

Then the chances are you have 2 versions of Groovy being used.
1 pre Groovy 2.3.5, and 1 after it.

Reminder: use this to investigate (remember to look at parents too)
mvn dependency:tree -Dverbose

I believe this is a Java 8 compatibility change, but would need to investigate to be sure.

Anyway, go here to find out more:
http://glaforge.appspot.com/article/groovy-2-3-5-out-with-upward-compatibility 


3 comments:

  1. Interesting post. Version compatibility between tools like Groovy and Eclipse can sometimes be tricky, so explanations like this are really helpful for developers trying to avoid compiler conflicts. Continuous learning is important in tech too—many people also explore practical skills through programs like Data Science, Full Stack Development, or Digital Marketing.

    ReplyDelete
  2. Dependency conflicts can be particularly difficult to diagnose when different versions of the same library are introduced through direct and transitive dependencies. The example of Groovy's ShortTypeHandling class shows why checking the complete Maven dependency tree, including parent dependencies, can be an important debugging step.

    For developers working with Java-based web applications, understanding how frameworks and dependencies fit together is an important part of maintaining a reliable development environment. A JAX-RS Angular Full Stack Developer Course can provide broader exposure to Java-based application development and related technologies.

    ReplyDelete