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

Using the Jetty plugin

In the previous section, we created a Java project with a web subproject. The web project has a simple servlet. To execute the servlet, we must create a WAR file and deploy the WAR file to a servlet container, such as Tomcat or Jetty. You can learn more about Jetty at http://www.eclipse.org/jetty/. With the Jetty plugin, we can run our web project from the command line in a Jetty web container. We don't have to install Jetty on our computer, we only need to apply the Jetty plugin to our project. The plugin will take care of configuring Jetty and starting the web container. If everything is okay, we can open a web browser and access our servlet.

To add the Jetty plugin to our web project, let's create a new build.gradle file in the web directory. Here, we will use the apply() method to add the Jetty plugin to the project:

apply plugin: 'jetty'

The plugin adds the following tasks to our project: jettyRun, jettyRunWar, and jettyStop. The following table shows the different...

Previous Section
End of Section 4
Next Section