Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Gradle Effective Implementations Guide - Second Edition

By : Hubert Klein Ikkink

4.3 (3)

Gradle Effective Implementations Guide

4.3 (3)

By: Hubert Klein Ikkink

Overview of this book

Gradle is a project automation tool that has a wide range of applications. The basic aim of Gradle is to automate a wide variety of tasks performed by software developers, including compiling computer source code to binary code, packaging binary codes, running tests, deploying applications to production systems, and creating documentation. The book will start with the fundamentals of Gradle and introduce you to the tools that will be used in further chapters. You will learn to create and work with Gradle scripts and then see how to use Gradle to build your Java Projects. While building Java application, you will find out about other important topics such as dependency management, publishing artifacts, and integrating the application with other JVM languages such as Scala and Groovy. By the end of this book, you will be able to use Gradle in your daily development. Writing tasks, applying plugins, and creating build logic will be your second nature.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Starting with Gradle

1. Starting with Gradle

Declarative builds and convention over configuration

Getting started

Writing our first build script

Default Gradle tasks

Task name abbreviation

Executing multiple tasks

Command-line options

Understanding the Gradle graphical user interface

Summary

2. Creating Gradle Build Scripts

2. Creating Gradle Build Scripts

Writing a build script

Defining tasks

Build scripts are Groovy code

Defining dependencies between tasks

Setting default tasks

Organizing tasks

Adding tasks in other ways

Accessing tasks as project properties

Adding additional properties to tasks

Avoiding common pitfalls

Skipping tasks

Summary

3. Working with Gradle Build Scripts

3. Working with Gradle Build Scripts

Working with files

Project properties

Using logging

Using the Gradle Wrapper

Summary

4. Using Gradle for Java Projects

4. Using Gradle for Java Projects

Why plugins?

Getting started with the Java plugin

Working with source sets

Working with properties

Creating Javadoc documentation

Summary

5. Dependency Management

5. Dependency Management

Dependency configuration

Repositories

Defining dependencies

Summary

6. Testing, Building, and Publishing Artifacts

6. Testing, Building, and Publishing Artifacts

Testing our projects

Running Java applications

Publishing artifacts

Packaging Java Enterprise Edition applications

Summary

7. Multi-project Builds

7. Multi-project Builds

Working with multi-project builds

Working with Java multi-project builds

Using the Jetty plugin

Summary

8. Mixed Languages

8. Mixed Languages

Using the Groovy plugin

Using the Scala plugin

Summary

9. Maintaining Code Quality

9. Maintaining Code Quality

Using the Checkstyle plugin

Using the PMD plugin

Using the FindBugs plugin

Using the JDepend plugin

Using the CodeNarc plugin

Summary

10. Writing Custom Tasks and Plugins

10. Writing Custom Tasks and Plugins

Creating a custom task

Creating a task in a standalone project

Creating a custom plugin

Creating a plugin in the project source directory

Creating a plugin in a standalone project

Summary

11. Gradle in the Enterprise

11. Gradle in the Enterprise

Creating a sample project

Using Jenkins

Using JetBrains TeamCity

Using Atlassian Bamboo

Summary

12. IDE Support

12. IDE Support

Using the Eclipse plugin

Using the IntelliJ IDEA plugin

Running Gradle in Eclipse

Running Gradle in IntelliJ IDEA

Summary

Customer Reviews

4.3 (3)

5 star

33.3%

4 star

66.7%

3 star

0%

2 star

0%

1 star

0%

Build scripts are Groovy code

We must keep in mind that Gradle scripts use Groovy. This means that we can use all the Groovy's good stuff in our scripts. We already saw the use of so-called Groovy GString in our sample script. The GString object is defined as a String with double quotes and can contain references to variables defined in a ${... } section. The variable reference is resolved when we get the value of the GString.

However, other great Groovy constructs can also be used in Gradle scripts. The following sample script shows some of these constructs:

task numbers << { 
    // To define a range of numbers 
    // we can use the following syntax: 
    // start..end. 
    // The each method executes the code 
    // in the closure for each element 
    // in a collection, like a range. 
    (1..4).each { number -> 
        // def is short for define. 
        // Used to define a variable without 
        // an explicit type of the variable. 
        def...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Gradle Effective Implementations Guide

Search

Your notes and bookmarks