Book Image

Gradle Essentials

By : Abhinandan Maheshwari
Book Image

Gradle Essentials

By: Abhinandan Maheshwari

Overview of this book

Gradle is an advanced and modern build automation tool. It inherits the best elements of the past generation of build tools, but it also differs and innovates to bring terseness, elegance, simplicity, and the flexibility to build. Right from installing Gradle and writing your first build file to creating a fully-fledged multi-module project build, this book will guide you through its topics in a step-by-step fashion. You will get your hands dirty with a simple Java project built with Gradle and go on to build web applications that are run with Jetty or Tomcat. We take a unique approach towards explaining the DSL using the Gradle API, which makes the DSL more accessible and intuitive. All in all, this book is a concise guide to help you decipher the Gradle build files, covering the essential topics that are most useful in real-world projects. With every chapter, you will learn a new topic and be able to readily implement your build files.

Related Content you might be interested in

Current Title:

Small book image
Gradle Essentials
Abhinandan Maheshwari
Dec, 2015 | 176 pages
No titles found
Table of Contents (17 chapters)
Gradle Essentials
Gradle Essentials
Credits
Credits
About the Authors
About the Authors
Acknowledgments
Acknowledgments
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Running Your First Gradle Task
Running Your First Gradle Task
Installing Gradle
The Gradle command-line interface
The first Gradle build script
Summary
2
Building Java Projects
Building Java Projects
Building a simple Java project
Unit testing
Bundling an application distributable
Generating IDE project files
Summary
3
Building a Web Application
Building a Web Application
Building a simple Java web project
References
Project dependencies
Summary
4
Demystifying Build Scripts
Demystifying Build Scripts
Groovy for Gradle build scripts
Gradle – an object-oriented build tool
Build phases
Gradle Project API
Tasks
References
Summary
5
Multiprojects Build
Multiprojects Build
The multiproject directory layout
The settings.gradle file
Organizing build logic in multiproject builds
Summary
6
The Real-world Project with Gradle
The Real-world Project with Gradle
Migrating from an Ant-based project
Migrating from a Maven project
Publishing artifacts
Continuous Integration
Generating documentation
Summary
7
Testing and Reporting with Gradle
Testing and Reporting with Gradle
Testing with TestNG
Integration testing
Code coverage
Code analysis reports
Summary
8
Organizing Build Logic and Plugins
Organizing Build Logic and Plugins
Extracting build logic to buildSrc
The first plugin
Configuring plugins
Summary
9
Polyglot Projects
Polyglot Projects
The polyglot application
Building Groovy projects
Building Scala projects
Joint compilation
References
Summary
Index
Index

Code coverage

There are so many coverage tools available for source code analysis such as EMMA, Corbatura, JaCoCo, and so on. In this section, we'll cover Gradle integration with JaCoCo to find the source code analysis.

Before we get started, we need to understand what code coverage is and why it is important in the test-driven development.

Code coverage is a metric that we can use to check how much of the source code was tested. Higher code coverage means a greater percentage of our code has been tested. Code coverage is typically done in the unit testing cycle. During code coverage, a developer must ensure that different logical paths in the source code have been tested and verified to achieve better code coverage.

Here, it is important to understand that the code coverage is not directly related to code quality. High code coverage does not guarantee that the quality code has been written. A developer must use static code analysis tools such as PMD (https://pmd.github.io/) to find the quality...

Previous Section
End of Section 4
Next Section