Gradle in Action is a comprehensive guide to end-to-end project automation with Gradle. Starting with the basics, this practical, easy-to-read book discusses how to build a full-fledged, real-world project. Along the way, it touches on advanced topics like testing, continuous integration, and monitoring code quality. You'll also explore tasks like setting up your target environment and deploying your software.
About the Technology
Gradle is a general-purpose build automation tool. It extends the usage patterns established by its forerunners, Ant and Maven, and allows builds that are expressive, maintainable, and easy to understand. Using a flexible Groovy-based DSL, Gradle provides declarative and extendable language elements that let you model your project's needs the way you want.
About the Book
Gradle in Action is a comprehensive guide to end-to-end project automation with Gradle. Starting with the basics, this practical, easy-to-read book discusses how to establish an effective build process for a full-fledged, real-world project. Along the way, it covers advanced topics like testing, continuous integration, and monitoring code quality. You'll also explore tasks like setting up your target environment and deploying your software.
The book assumes a basic background in Java, but no knowledge of Groovy.
Purchase of the print book includes a free eBook in PDF, Kindle, and ePub formats from Manning Publications.
Whats Inside
A comprehensive guide to Gradle Practical, real-world examples Transitioning from Ant and Maven In-depth plugin development Continuous delivery with Gradle
About the Author
Benjamin Muschko is a member of the Gradleware engineering team and the author of several popular Gradle plugins.
Table of Contents
PART 1 INTRODUCING GRADLE Introduction to project automation Next-generation builds with Gradle Building a Gradle project by example PART 2 MASTERING THE FUNDAMENTALS Build script essentials Dependency management Multiproject builds Testing with Gradle Extending Gradle Integration and migration PART 3 FROM BUILD TO DEPLOYMENT IDE support and tooling Building polyglot projects Code quality management and monitoring Continuous integration Artifact assembly and publishing Infrastructure provisioning and deployment
Tedious and verbose. I just don't understand the philosophy of any of these "in Action" books and I've tried reading 3 of them. They'll tell you that the Animal kingdom is huge but then go on and examine only Koala bears. You get no higher sense of the properties and behaviors that are prevalent in the Animal kingdom. And because of the conversational/story telling style, information is scattered about. Never again will I pick up one of these "in Action" books. If you love the style of presentation of classic Unix and C books, you will hate the style of presentation of these "in Action" books.
The first half was very interesting. Some stuff was obsolete, but it was still really good read. I wish the book would be updated with latest version of Gradle. Other half about automation, deployment, provisioning was not really interesting. It describes one way to build and deploy software (which is probably obsolete now).
The first chapter may look tedious, but if you worked with Ant and Maven before, and know their philosophy, then it really worth it. The next chapter guides you to think about treating the build script as an object, because it is Groovy, and strive for declaration over iteration. Then for the rest, it is bit obsolete comparing to now. Because it was written 7 years ago :P
An OK book that has lots of useful information. But it wasn't as concise as I'd have liked and it tried too hard to drive home the point that Gradle is much better than ant and maven, rather than arguing that it's more flexible or that it's the tool to use when your problem exceeds the scope of what maven can do. (Note: my comments are based on a Aug 2013 MEAP version, so the book may have improved since)
This is a very thorough book about Gradle. It describes various scenarios where one could use a build tool like Gradle. It described how Gradle, specifically, can be used to solve those problem. After reading this you should be able to do just about whatever you need to do with Gradle. The bonus is that there are many other useful development tools discussed along the way that can aid in other development areas (especially Java related tools).
I found it bizarre that the explanation of Gradle syntax (how it relates to groovy) was buried in a brief appendix, when it is what you need to understand in order to confidently go beyond the samples provided. Meanwhile the main text is full of tedious explanations and tangential discussions that only barely relate to understanding Gradle.
I am not sure for whom the book is. It describes the concept of repositories for beginners on one hand and advanced stuff like puppet on the other hand.