Whether you use a mono-repository or multi-repository approach for your sources, managing dependencies is central to productivity by reusing artifacts and ensuring a quality build.
Today, we’re excited to announce a big step towards our mission to transform how software is built and shipped. We recognize that not all teams are using Gradle or are in a position to migrate soon. In this blog post, we’ll learn how you can utilize the insights provided by build scans and the acceleration of the build cache in Apache Maven™ builds.
Build cache infrastructure can be critical to accelerate your builds. But don’t expect to achieve your maximum potential build acceleration right out of the box.
Hell has frozen over. Gradle Enterprise supports Apache Maven!
Hell has frozen over. Gradle Enterprise will soon support Apache Maven™. Users will get faster Maven builds and fine-grained build analysis without having to migrate.
Gradle 5.0 is much faster and more memory efficient than previous versions of Gradle, has better tools to inspect and manage transitive dependencies, and can provide the IDE assistance you’d always hoped and expected through a new Kotlin DSL.
We are excited to tell you about some big updates to Gradle Enterprise!