June 2019

Table of Contents

Introduction

Welcome to the June 2019 newsletter.

This issue covers the Gradle 5.5 RC1, Gradle Enterprise 2019.2 release, and various community news.

New Gradle content

From the community

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 Enterprise 2019.2

The newest Gradle Enterprise release 2019.2 includes a new build performance trend dashboard, several new features for Maven users, significant improvements to caching for various popular Maven plugins, and the ability to run Gradle build scans for composite and continuous builds.

The blog post Monitoring build performance trends using Gradle Enterprise walks you through how to use the new dashboards to tell whether your builds are slowing down over time and how to pinpoint what might be contributing to the slowdown.

For Maven users, several features previously only available for Gradle builds were added in Gradle Enterprise 2019.2. This includes the performance dashboard and goal inputs comparison, an invaluable view for debugging cache misses. In addition, several maven plugins such as Javadoc, Checkstyle, and JAXB2 are now cacheable.

Gradle users can now take advantage of build scans for composite and continuous builds.

For more detailed information on the changes in this release, see the Gradle Enterprise 2019.2 release notes.

Gradle 5.5 RC1

Gradle 5.5 RC1 includes:

To find out about the other new features and bug fixes included in Gradle 5.5 RC1, see the release notes.

Upcoming events

Job opportunities

Gradle employees are distributed all over the world so, in early May, we met at a rustic farmhouse outside Barcelona for our yearly World Meeting. If you want to join next year’s world meeting, apply today for one of the open positions listed below.

The details of these and other open positions 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 Build Tool Team

If you have some news you’d like us to share in the next issue, let us know using the #community-news channel on the Gradle Community Slack or by mentioning @Gradle on Twitter/X.

Until next time!
— The Gradle Team