Welcome to the February Newsletter!
From the community
We ❤️ you Gradle community! Thank you for your blog posts and contributions!
- Reproducible Builds in Java — In this post, Maria Camenzuli demonstrates the value of reproducible builds, and explains how to make your Java build reproducible using Gradle.
- Renaming Your Gradle Build Files — Philippe Breault proposes a naming convention for
.gradlescripts that makes it obvious which subproject each one configures.
- Dockerizing a Spring Boot application and Integration testing using containers — 2 great blog posts about using Docker with Gradle, by Ben Muschko.
- Setting Up a Microservices Architecture with Spring Boot and Gradle — Akash Bhingole explains and codifies microservices architecture through an example using Spring Boot and Gradle.
- Kotlin + buildSrc for Better Gradle Dependency Management — In this article, Sam Edwards achieves IDE completion for a set of dependencies by declaring Kotlin constants under
buildSrc— very clever.
Have a blog post or plugin you’d like to see featured here? Just send us an email with the details to firstname.lastname@example.org.
Gradle 4.6 is a big release.
- JUnit Platform (aka JUnit 5) Support
--fail-fastfor Test tasks
- Custom command-line flags for custom tasks
- Experimental BOM and optional dependencies support
- Customizable metadata file resolution
- Improved Visual Studio support for multi-project builds
- Kotlin DSL support for init scripts
Gradle Enterprise 2018.1
When using build scan plugin 0.12.1+, you will see:
- Included builds in the project view
- Tasks from included builds in the tasks view
- Which dependencies were substituted by an included build
More details are available in the release notes.
Kotlin Build Caching
Build caching is particularly effective when a CI instance populates a shared, remote build cache. Community members have written 2 tutorials for doing just that:
Upcoming online training
- Mar 13-14: Introduction to Gradle
- Apr 17-20: Advanced Gradle Fundamentals for Java/JVM
- Anytime: Maximizing Developer Productivity with Gradle Enterprise
Until next time!
—The Gradle Team