August 2019

Welcome to the August 2019 newsletter.

This issue covers the Gradle 5.6 release, Gradle Enterprise 2019.3 release, and how to fix broken builds using Gradle Enterprise.

From the community

• A Bootiful Podcast: Gradle Developer Advocate Jenn Strater - Gradle Developer Advocate Jenn Strater chats with Spring Developer Advocate Josh Long about Gradle, Gradle Enterprise, and more.
• Pollution-Free Dependency Management with Gradle - a blog post from Tom Hombergs showing how to use Gradle’s implementation configuration to prevent leaking dependencies onto the compile-time classpath of other dependencies.
• Maven Scopes and Gradle Configurations Explained - another blog post from Tom Hombergs. This one explains the differences between Maven Scopes and Gradle Configurations.
• Dagger 2.24 - “Gradle’s incremental annotation processing is now enabled for all builds”.

If you have a talk, blog post, or plugin release you’d like us to share in the next issue, use #gradle on Twitter or send us an email with the details to newsletter@gradle.com.

Gradle hits 10 million monthly downloads! 🎉

Gradle continues to see growing download numbers. For several months this year, Gradle hit 10+ million monthly downloads – nearly double where we were at the same time last year. Congrats to the team for this achievement and thanks to everyone who advocates for Gradle build tool usage in the community.

Gradle 5.6

Gradle 5.6 is out. This is the final Gradle 5 release before 6.0. You may want to check out the deprecations list as these will be important for Gradle 6 migration.

The top features of the Gradle 5.6 release are:

• test fixtures for Java projects
• plugin management via settings file
• faster Groovy compilation (via experimental and incubating features)

We also recommend checking out PMD incremental analysis, executable Jar support, support for failing the build on deprecation warnings, and the section on improvements for plugin authors.

As with all releases, please upgrade to the newest version to take advantage of these new features and improvements.

./gradlew wrapper –gradle-version=5.6

Gradle Enterprise 2019.3

Gradle Enterprise, our SaaS platform of data and infrastructure services that customers use to accelerate and optimize Gradle and Apache Maven™ builds, released version 2019.3.

This release includes many exciting new features including:

• build failure analysis
• enhanced Gradle dependency insights
• dependency download time visualization
• build logic dependencies insights
• console log view and tests view for Maven build scans
• and more!

We have published a blog post to help you understand how you can fix broken builds using Gradle Enterprise.

Upcoming events

• August 29: Einführung in Gradle (Deutsch/German) - Gradle engineer Benedikt Ritter will present at the Rhein JUG.
• August 30: Gradle and Kotlin (Englisch/English) - Gradle Engineer Jendrik Johannes will present at Kotlin/Everywhere Hamburg.
• September 5: Developer Productivity Engineering – How to Maintain Performance As the Codebase Grows - an online webinar from Gradle.
• September 10-11: Introduction to Gradle - official online Gradle training.
• September 12: CloudBees Days: London
• September 24: CloudBees Days: Frankfurt
• September 25: Build Cache Deep Dive - official online Gradle training.
• September 26: CloudBees Days: Stockholm
• September 27-29: NFJS Boston
• October 7-10: SpringOne Platform
• October 25-26: NFJS Chicago
• October 28-30: DevOps Enterprise Summit: Las Vegas

Job opportunities

The Gradle Inc. engineering team continues to grow. We’re currently looking for:

• Gradle Enterprise (remote/worldwide) – Solutions Engineer
• Gradle Enterprise (remote/worldwide) – Back-end and Front-end Software Engineers
• Gradle Build Tool (remote/worldwide) – Software Engineer

The details of these and other open positions are available at gradle.com/careers.

---

If you have some news you’d like us to share in the next issue, use #gradle on Twitter or send us an email with the details to newsletter@gradle.com.

Until next time!

—The Gradle Team