This Webinar is the first part of a in-depth discussion of important power features added in Gradle 1.0. We talked about the new local dependency cache, the improved change detection, dynamic versions and modules and conflict resolution. Further more we gave a brief introduction of the Gradle daemon.
In this webinar, Gradle Core Developer Szczepan Faber talked about strategies and techniques to reduce dramatically the risk of migrating your build to Gradle, and to make it a pleasant and seamless experience for everyone. Szczepan also unveiled the truly revolutionary practice of test-driven build migration using our soon-to-be-released Migration Plugin and DSL.
To wrap up a great year for Gradle, we thought it would be fun to look at how the Gradle team eats its own dog food.
Gradle is the next step in JVM-based build tools. It draws on lessons learned from established build tools like Ant and Maven, incorporating and improving upon their best ideas, like full flexibility and convention over configuration. In Gradle you declaratively model your problem domain using a powerful Groovy DSL instead of cumbersome XML. As a result, your builds are far more expressive, extensible, and testable.
Empower yourself to automate your build
Gradle is the next generation in build automation. It uses convention-over-configuration to provide good defaults, but is also flexible enough to be usable in every situation you encounter in daily development. Build logic is described with a powerful DSL and empowers developers to create reusable and maintainable build logic.
Build and test software written in Java and many other languages with Gradle, the open source project automation tool that’s getting a lot of attention. This concise introduction provides numerous code examples to help you explore Gradle, both as a build tool and as a complete solution for automating the compilation, test, and release process of simple and enterprise-level applications.
Discover how Gradle improves on the best ideas of Ant, Maven, and other build tools, with standards for developers who want them and lots of flexibility for those who prefer less structure.