Backend Development 3 min read

Apache Groovy 4.0.0 RC2 Released with Improvements and Dependency Updates

Apache Groovy 4.0.0 RC2 has been announced, featuring language enhancements such as new compilation behavior for operators and method naming, along with extensive upgrades to build, test, and runtime dependencies across the project.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
Apache Groovy 4.0.0 RC2 Released with Improvements and Dependency Updates

Apache Groovy 4.0.0 RC2 has been released, bringing several language improvements and a series of dependency upgrades.

Improvements

[GROOVY-10383] – SC: !in compiled to ScriptBytecodeAdapter#isNotCase

[GROOVY-10395] – SC: <=> compiled to ScriptBytecodeAdapter#compareTo for primitives

[GROOVY-10401] – Prevent Groovy console from popping up during minimization

[GROOVY-10417] – MethodNode toString() adds quotes when name contains spaces or non‑identifier characters

[GROOVY-10418] – Introduce `src/antlr` in jar source

Dependency upgrades

[GROOVY-10397] – Bump JUnit to 5.8.2

[GROOVY-10399] – Bump Bridger to 1.6.Final

[GROOVY-10400] – Bump Gradle to 7.3.1

[GROOVY-10402] – Bump JarJar to 1.8.0

[GROOVY-10408] – Bump Log4j2 to 2.15.0

[GROOVY-10410] – Bump Log4j2 to 2.16.0

[GROOVY-10416] – Bump Logback to 1.2.8

[GROOVY-10420] – Bump Gradle to 7.3.2

[GROOVY-10421] – Bump Jqwik to 1.6.1

[GROOVY-10422] – Bump Spotbugs/Spotbugs annotations to 4.5.2

[GROOVY-10423] – Bump Checkstyle to 9.2

[GROOVY-10425] – Bump Log4j2 to 2.17.0

[GROOVY-10426] – Bump Jqwik to 1.6.2

[GROOVY-10427] – Bump Jackson to 2.13.1

[GROOVY-10430] – Bump Gradle to 7.3.3

[GROOVY-10432] – Bump HSQLDB to 2.6.1

JavaJVMreleaseGroovyDependency Upgraderc2
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.