Upgrading groovy from 2.4 to 3.0 , why Intellij complains about could not resolve groovy-all-3.0.15-indy.jar?

Question

I am upgrading a Spring MVC application from Java 1.8 to Java 17. I have tried to update the groovy version from 2.4.x to 3.0.15. If I run the clean build, either from IntelliJ terminal or Mac command prompt, the build runs, but if I refresh using the Gradle refresh image shown on the gradle file, there is an update and the build fails with the following exception:

Could not find groovy-all-3.0.15-indy.jar (org.codehaus.groovy:groovy-all:3.0.15).
Searched in the following locations:
    https://repo1.maven.org/maven2/org/codehaus/groovy/groovy-all/3.0.15/groovy-all-3.0.15-indy.jar

I do understand that indy.jar is not part of groovy, but why is IntelliJ trying to get indy.jar?

I have tried to change grooy-all to groovy, but the build needs other dependencies which are bundled with groovy-all.

Answer 1

the groovy-all jar was deprecated from V2.5. The different libraries are split into separate jars. You can use the groovy-all Gradle pom dependency here if you want all.

More info here.

Indy (InvokeDynamic) has also been dropped because of a dependency on a higher than 1.8 java version.