Welcome to the November 2022 Gradle Build Tool newsletter. This edition covers news from the community, some highly used plugins, and some semantic versioning insights. It also shares some blog posts from the Gradle Build Tool team, a What is Gradle Build Tool video, and a request to help us improve our documentation by completing the Gradle Documentation Survey 2022.
From the Community
- Gradle Goodness: Defining Plugin Versions Using Version Catalog — Provides a clear example of how to use a version catalog to manage plugin versions.
- Making Gradle Inputs Just Sensitive Enough — Describes why “absolute vs relative paths” matter for caching and how to change the settings to meet your needs.
- Create Webjar With Gradle and GitHub Packages — Shows how to create WebJars from scratch and publish the package to GitHub.
- Fixing Dependency Metadata in Gradle — Takes a deep dive into dependency metadata and learn why you might want to use component metadata rules.
- Gradle Composite Build Instead of Mono-Repository — Describes how to use composite builds for Android projects.
- Understanding Gradle #25 – Using Java to Configure Builds — Provides a guide to configuring Gradle with plain Java without Kotlin or Groovy DSL.
- Gradle Course for Beginners — Gets you started with a full 70-minute course on the Gradle Build Tool by tomgregory.com.
- GradleX Build Parameters Plugin — Use Version 1.3 of this popular plugin for compile-safe access to parameters that adds some extra cachability and descriptions for groups.
- Android Root Coverage Plugin — Leverage this plugin to facilitate Jacoco configuration for Android projects by automatically setting up code coverage tasks for combined and per module coverage reports.
A question arose around how various libraries use different styles of semantic versioning. The community come up with some solutions:
- Semantic Versioning in Java — Run this Kotlin script to turn diverse semver strings into sortable objects.
- Comparing Version Sorting on the JVM — Use this repository to get another take at a semver solution by adding some other implementations.
From Gradle Team
- How We Handle Flaky Tests in Gradle — Learn about a few strategies to address automated test flakiness challenges.
- Introducing Test Suites — Test Suites have been around for about a year, have you had a chance to explore them yet? Read this post to learn best practices for wrangling your project’s testing setup and hear a few hints at the future of testing with Gradle.
- What is the Gradle Build Tool? A Simplified Explanation — Get a non-technical explanation of why we need build software. How does code become an app? What is the Gradle Build Tool?
- Gradle Documentation Survey 2022 — Help us improve our documentation by completing this survey!
If you share our passion for developer productivity and tooling, consider joining our globally distributed team and check out our job openings at gradle.com/careers. We are looking for software engineers, solutions engineers, application security engineers, and developer productivity engineers.
See the Gradle Training webpage for an up-to-date list of all upcoming educational and training events. Here is a highlight of some of the next ones:
- November 29, 11:00 am - 2:00 pm (US EDT): Virtual Workshop — Gradle Build Cache Deep Dive
- November 30, 12:00 pm - 2:30 pm (US EDT): Virtual Training — Introduction to Developer Productivity Engineering
- December 1, 9:00 am - 10:00 pam (US EDT): Virtual Training — Gradle Enterprise Training for Developers
- December 7, 12:00 pm - 1:30 pm (US EDT): Virtual Training — Configuring Gradle Build Tool with Kotlin Course
- December 7, 9:15 am - 10:00 am (US EDT): Conference Presentation — Developer Productivity Engineering in Practice
- December 8, 10:00 pm - 2:00 pm (US EDT): Virtual Workshop — Introduction to Gradle Build Tool
- December 13, 4:00 pm - 8:00 pm (US EDT): Virtual Workshop — JVM Builds with Gradle Build Tool
- December 19, 11:00 am - 3:00 pm (US EDT): Virtual Workshop — Advanced Dependency Management
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 firstname.lastname@example.org.
Until next time!
—The Gradle Build Tool Team