Gradle in Action (Anglais) Broché – 6 mars 2014
|Neuf à partir de||Occasion à partir de|
- Choisissez parmi 17 000 points de collecte en France
- Les membres du programme Amazon Prime bénéficient de livraison gratuites illimitées
- Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
- Sélectionnez cette adresse lors de votre commande
Les clients ayant consulté cet article ont également regardé
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Description du produit
Présentation de l'éditeur
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, problem domains are declaratively modeled using a powerful Groovy DSL instead of cumbersome XML. As a result, builds are far more expressive, extensible, and testable.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. It also covers tasks like setting up target environments and deploying software.
RETAIL SELLING POINTSPractical real-world examples
Gradle from the ground upTakes software delivery processes to the next level.
No prior experience with Groovy required. This book assumes basic knowledge of Java.
ABOUT THE TECHNOLOGY
Build automation is key to implementing Continuous Delivery, a hot topic these days. Enterprises want to ship software, fast and repeatable. Gradle, a powerful and expressive build tool, plays an important role as an enabling tool to support the build and deployment process.
Biographie de l'auteur
AUTHOR BIOBenjamin Muschko is a senior software engineer with more than 10 years of experience in developing and delivering business applications. He is an active Gradle contributor and author of several popular plugins.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
|5 étoiles (0%)|
|4 étoiles (0%)|
|3 étoiles (0%)|
|2 étoiles (0%)|
|1 étoile (0%)|
Commentaires client les plus utiles sur Amazon.com
My biggest complaint was it was very difficult to find the technical details you need to actually use Gradle.
He talks endlessly about Gradle without giving you the raw technical details you need to really use it.
I would read about Gradle concepts but then to actually use them I had to Google them to get real usable information.
The other thing the bothered me is he would present "examples" that were incomprehensible then tell you "don't worry if you don't understand this" and never explain it. I'm reading the book to gain understanding - why give examples that don't lead to greater understanding?
I found there were cases that after I Googled it and found how to accomplish a task, I went back and re-read the chapter and discovered he had actually give the information - it just wasn't presented in a manner that was usable for someone who didn't already know how to use it.
My background: I've used Ant and Maven for years, but I had no previous exposure to Groovy.
I found that this book provides excellent coverage of Gradle and how it can be used across a Continuous Delivery pipeline. I was satisfied with the level that the author covered the various topics. He never went too deep into a subject, and when he stopped the discussion he always provided a link to where I could find additional information.
Here are some of the aspects of the book I enjoyed:
* The presentation style is very similar to a programming book. Which makes sense since Gradle is a DSL in Groovy.
* I liked the mild introductions to various concepts (Project Automation, Build Tools, Dependency Management, Automated Testing, Continuous Integration/Delivery).
* The source code is available in a Git repository (updates are as simple as a "git pull" command).
* He uses a common "ToDo" project throughout the book, updating the project as it applies to the subject being covered.
* Exposure to other tools in the examples (Junit, TestNG, Spock, CloudBees, Jenkins, ...). In chapter 8 you create a plugin to publish a WAR file to the Cloud (CloudBees). In Chapter 13 you are lead through the process of building the ToDo project with Jenkins, which I thought was AWESOME!
* The Appendix on Groovy was short, yet in depth enough to understand the Gradle syntax. The author also suggests looking at the DZone cheat sheet for Groovy.
I think this book is a good addition to my library.