Time for a makeover

Gradle 4.9 is here: Fixed leaks, experimental new task API and so much more

© Shutterstock /Olga_Angelloz (modified)  

Gradle is here with the newest release 4.9 and it impresses us with an extensive list of new features, improvements, issue fixes, and a couple of breaking changes!

Our beloved automation system is back with a fresh update!

Gradle 4.9 has been released and it is fully packed with awesome and handy new features, updates and improvements!

Among others, Gradle publication tools are getting an impressive make-over with projects that publish auxiliary publications throughmaven-publish and ivy-publishnow being able to be depended upon by other projects in the same build. What’s more, there is also a new Publishing Overview chapter in the user manual and updates throughout the documentation regarding publishing artifacts using Maven and Ivy.

Let’s take a closer look at all that’s new in Gradle 4.9.

New and noteworthy features

As mentioned before, this release is a really stuffed one with tons of amazing new things:

Command line args supported by JavaExec – Command line arguments can be passed to JavaExec with --args.

Improved dependency insight report – The dependency insight report is the distant ancestor of build scans and helps you diagnose dependency management problems locally. This release of Gradle implements several improvements. have a look at the full list here.

Continuing development of Native ecosystem – The Gradle Native project continues to improve and evolve the native ecosystem support for Gradle.

Faster clean checkout builds – Gradle now stores more state in the Gradle user home instead of the project directory. Clean checkout builds on CI should now be faster as long as the user home is preserved.

Java and Groovy compiler no longer leaks file descriptors – Leaks fixed! If you had switched to forking mode because of this problem, it is now safe to switch back to in-process compilation.

SEE ALSO: Build Gradle projects with Eclipse Buildship

Experimental new task API – In a nutshell, the new task API allows builds to avoid the cost of creating and configuring tasks when those tasks will never be executed.

Dependency insight report – The dependency insight report is now considered stable.

Tooling API types and methods – Many types and methods that were previously marked @Incubating are now considered stable.

Breaking news part 1- EclipseProject tasks defined for gradle eclipse may now run in Buildship.

Breaking news part 2 – You can start using Groovy GPath with tasks.withType().

But that’s not all.

There is a quite extensive list of issues that have been fixed in Gradle’s latest version; 31 to be precise! Check out the full list here.

If you cannot wait to try out the latest version of Gradle, switch your build to use Gradle 4.9 quickly by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.9

Standalone downloads are available at

Eirini-Eleni Papadopoulou
Eirini-Eleni Papadopoulou was the editor for Coming from an academic background in East Asian Studies, she decided that it was time to go back to her high-school hobby that was computer science and she dived into the development world. Other hobbies include esports and League of Legends, although she never managed to escape elo hell (yet), and she is a guest writer/analyst for competitive LoL at TGH.

Inline Feedbacks
View all comments