Book Image

Gradle Effective Implementations Guide - Second Edition

By : Hubert Klein Ikkink
Book Image

Gradle Effective Implementations Guide - Second Edition

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.

Related Content you might be interested in

Current Title:

Small book image
Gradle Effective Implementations Guide - Second Edition
Hubert Klein Ikkink
May, 2016 | 368 pages
No titles found
Table of Contents (18 chapters)
Gradle Effective Implementations Guide - Second Edition
Gradle Effective Implementations Guide - Second Edition
Credits
Credits
About the Author
About the Author
About the Reviewer
About the Reviewer
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Starting with Gradle
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
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
Working with Gradle Build Scripts
Working with files
Project properties
Using logging
Using the Gradle Wrapper
Summary
4
Using Gradle for Java Projects
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
Dependency Management
Dependency configuration
Repositories
Defining dependencies
Summary
6
Testing, Building, and Publishing Artifacts
Testing, Building, and Publishing Artifacts
Testing our projects
Running Java applications
Publishing artifacts
Packaging Java Enterprise Edition applications
Summary
7
Multi-project Builds
Multi-project Builds
Working with multi-project builds
Working with Java multi-project builds
Using the Jetty plugin
Summary
8
Mixed Languages
Mixed Languages
Using the Groovy plugin
Using the Scala plugin
Summary
9
Maintaining Code Quality
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
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
Gradle in the Enterprise
Creating a sample project
Using Jenkins
Using JetBrains TeamCity
Using Atlassian Bamboo
Summary
12
IDE Support
IDE Support
Using the Eclipse plugin
Using the IntelliJ IDEA plugin
Running Gradle in Eclipse
Running Gradle in IntelliJ IDEA
Summary

Summary

When we develop applications, we usually develop the code with an IDE. In this chapter, we saw how to use the Gradle plugins in Eclipse, Eclipse WTP, and IDEA to generate project files for Eclipse and IntelliJ IDEA.

The plugins have a DSL to change the configuration before the files are generated. We can also use hooks to change the model objects before and after the DSL is applied. At the lowest level, we can use the withXml hook to alter the XML content before the file is written to the disk.

Both Eclipse and IntelliJ IDEA have plugins to import an existing Gradle project. We can then work with the project from within the IDE. Extra dependencies or changes are reflected in the classpath project files so that the code can be compiled with the IDE's compiler. We can also run Gradle tasks from within the IDE, so we don't have to leave our favorite IDE if we want to use Gradle.

In this book, we have seen the power of Gradle as a build tool. The Gradle syntax is very consistent and compact...

Previous Section
End of Chapter 12
Next Chapter