Team Gradle has released a new version of their tool and that’s Gradle 4.9. Gradle is a build tool for build automation with multi-language development. It offers excellent flexibility to the complete development lifecycle.
As per the team, one of the quickest ways to update one’s build to use the new version is by updating the build wrapper properties as follows:
./gradlew wrapper --gradle-version=4.9
However, the standalone downloads are available at gradle.org/install
One can now pass command line arguments to JavaExec using –args. This means if one wants to launch their application using the command line arguments foo –bar, hardcoding it into the build script is not required. One just has to simply run gradle run –args ‘foo –bar.
This version features an improved dependency insight report including build scans. The report helps in easy diagnosis of dependency management problems, locally. Some improvements in this report include:
The Gradle Native project stays steady in order to improve and evolve the native ecosystem support for Gradle.
This version now stores more states in the Gradle user home instead of the project directory. This results in clean and faster checkout builds on CI as long as the user home is preserved.
By default, the Java and Groovy compilers both leak file descriptors during the run in-process. This, in turn, can lead to “cannot delete file” exceptions on Windows and “too many open file descriptors” on Unix.
In the Gradle 4.9, these leaks have been fixed. Users who had switched to forking mode because of this problem, can now safely switch back to in-process compilation.
Gradle 4.9 includes a new task API which allows builds to avoid the cost of creating and configuring tasks for the ones that will never be executed.
By upgrading to this new API, one can experience slightly faster configuration times. The benefits will keep improving as more plugins adopt this API.
Note that this API is in incubation and may change before Gradle 5.0.
This version includes some promoted features which were in incubation during the previous release. The promoted features which include a stable dependency insight report and the tooling API types and methods are now supported and stable. These two features are also subject to backward compatibility.
As per my past research on Gradle and observing its past release trends, it looks like we can expect Gradle 5.0 in August or September.
Read more about the other fixed issues and deprecations in the Gradle 4.9 release notes.
I remember deciding to pursue my first IT certification, the CompTIA A+. I had signed…
Key takeaways The transformer architecture has proved to be revolutionary in outperforming the classical RNN…
Once we learn how to deploy an Ubuntu server, how to manage users, and how…
Key-takeaways: Clean code isn’t just a nice thing to have or a luxury in software projects; it's a necessity. If we…
While developing a web application, or setting dynamic pages and meta tags we need to deal with…
Software architecture is one of the most discussed topics in the software industry today, and…