Gradle Effective Implementation Guide

Gradle Effective Implementation Guide

Overview of this book

Gradle is the next generation in build automation. It uses convention-over-configuration to provide good defaults, but is also flexible enough to be usable in every situation you encounter in daily development. Build logic is described with a powerful DSL and empowers developers to create reusable and maintainable build logic."Gradle Effective Implementation Guide" is a great introduction and reference for using Gradle. The Gradle build language is explained with hands on code and practical applications. You learn how to apply Gradle in your Java, Scala or Groovy projects, integrate with your favorite IDE and how to integrate with well-known continuous integration servers.Start with the foundations and work your way through hands on examples to build your knowledge of Gradle to skyscraper heights. You will quickly learn the basics of Gradle, how to write tasks, work with files and how to use write build scripts using the Groovy DSL. Then as you develop you will be shown how to use Gradle for Java projects. Compile, package, test and deploy your applications with ease. When you've mastered the simple, move on to the sublime and integrate your code with continuous integration servers and IDEs. By the end of the "Gradle Effective Implementation Guide" you will be able to use Gradle in your daily development. Writing tasks, applying plugins and creating build logic will be second nature.

Gradle Effective Implementation Guide

Credits

About the Author

Acknowledgement

About the Reviewers

www.PacktPub.com

Preface

Free Chapter

Starting with Gradle

Introducing Gradle

Getting started

Writing our first build script

Default Gradle tasks

Task name abbreviation

Executing multiple tasks

Command-line options

Understanding the Gradle user interface

Summary

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

Working with Gradle Build Scripts

Working with files

Project properties

Using logging

Using the Gradle wrapper

Summary

Using Gradle for Java Projects

Using plugins

Getting started

Using the Java plugin

Working with source sets

Working with properties

Creating documentation

Assembling archives

Summary

Dependency Management

Dependency configuration

Repositories

Defining dependencies

Summary

Testing, Building, and Publishing Artifacts

Testing

Running Java applications

Publishing artifacts

Packaging Java Enterprise Edition applications

Summary

Multi-project Builds

Working with multi-project builds

Working with Java multi-project builds

Using the Jetty plugin

Summary

Mixed Languages

Using the Groovy plugin

Using the Scala plugin

Summary

Maintaining Code Quality

Using the Checkstyle plugin

Using the PMD plugin

Using the FindBugs plugin

Using the JDepend plugin

Using the CodeNarc plugin

Using the Sonar plugin

Summary

Writing Custom Tasks and Plugins

Creating a custom task

Creating a task in the project source directory

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

Using Gradle with Continuous Integration

Creating a sample project

Using Jenkins

Using JetBrains TeamCity

Using Atlassian Bamboo

Summary

IDE Support

Using the Eclipse plugin

Using the IntelliJ IDEA plugin

Running Gradle in Eclipse

Running Gradle in IntelliJ IDEA

Summary

Index

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Using the CodeNarc plugin

To check code written in the Groovy language, we can use CodeNarc. CodeNarc has several rules to do a static analysis of Groovy code. Gradle has a CodeNarc plugin, so we can apply the rules from CodeNarc to our Groovy code base. If we apply the plugin, we automatically get a codenarcMain and codenarcTest target. Also, for each custom source set, we get a new task named codenarc<SourceSet>. All these tasks are dependency tasks of the check task.

The CodeNarc library is not included with Gradle. We need to define a repository in our build file that contains CodeNarc. If we invoke a codenarc task, then Gradle sets CodeNarc dependencies. We can change the version of CodeNarc that we want to use by setting the codenarc.toolVersion property.

The plugin defines that we provide a CodeNarc configuration file with the name codenarc.xml in the directory config/codenarc. We can change the reference to the configuration file with the configFile property of the plugin...

Gradle Effective Implementation Guide

Gradle Effective Implementation Guide

Overview of this book

Related Content you might be interested in

Current Title:

Gradle Effective Implementation Guide

Using the CodeNarc plugin