Task Dependencies: Gradle

Steven J Zeil

Last modified: Oct 24, 2020

Contents:

1 Gradle Overview

1.1 What to keep and leave from Ant

1.2 What to keep and leave from Maven

1.3 What does Gradle offer?

1.4 The Gradle Wrapper

2 gradle by example

2.1 Simple Java Build

2.2 Java Build with Third-Party Libraries

2.3 Java Build with Unit Tests

2.4 C++ Multi-project Build

3 Customizing Tasks

3.1 Gradle Tasks

3.2 Anatomy of a Task

3.3 Task Dependencies

Gradle is a build manager based upon an Ant-like task dependency graph expressed in a more human-friendly notation, with a Maven-like ability to express standard project layouts and build conventions.

1 Gradle Overview

Gradle devised by GradleWare, founded by Hans Dockter, released in 2012
Has become the standard build tool for Android
Tries to strike a middle ground between Ant and Maven

1.1 What to keep and leave from Ant

Keep:

Portability
- Build commands are described in a platform-independent manner.
Flexibility
- Almost any sequence of processing steps can be described.
- Allows for unconventional build sequences
- Allows for unconventional build targets

Leave

XML as a build language.

“XML was an easy choice for a build tool a decade ago, when it was a new technology, developers were enthusiastic about it, and no one yet knew the pain of reading it in large quantities. It seemed to be human-readable, and it was very easy to write code to parse it. However, a decade of experience has shown that large and complex XML files are only easy for machines to read, not for humans. Also, XML’s strictly hierarchical structure limits the expressiveness of the format. It’s easy to show nesting relationships in XML, but it’s hard to express program flow and data access the way most common programming language idioms express them. Ultimately, XML is the wrong format for a build file.”

Tim Berglund, Learning and Testing with Gradle

Inability to express simple control flow

e.g., loop through all files in a directory and do task

1.2 What to keep and leave from Maven

Keep:

Dependency management
- Gradle will work with Maven & Ivy repositories.
  - Early versions of Gradle actually used Ivy, though eventually it gained its own dependency manager.
Archetypes
- If your project has nothing unusual about its build, you can sit back and use the defaults.

Leave

XML as a build language.
Inflexibility
- If your project has anything unusual about its build, changing the defaults in Maven is frustrating.
Inability to express simple control flow

1.3 What does Gradle offer?

Build files are written in Groovy
- Groovy is a scripting language that runs in a Java JVM
  - Syntax is Java-based
  - Interfacing with Java code is easy
- Gradle adds build-specific functions as a Groovy library

1.4 The Gradle Wrapper

Suppose that you are building your project with Gradle.

Other people may try to check out a copy of your code, including your Gradle build file.
But maybe they won’t have Gradle on their machine.

If you set up your project with the Gradle Wrapper, you get a simple script named gradlew.

You invoke your build via ‘gradlew’ instead of ‘gradle’
- gradlew checks to see if the system on which it is running has Gradle installed.
  - If not, it downloads a copy and installs it under $USER_HOME/.gradle
- It then invokes gradle (old installation or new), passing any parameters you supplied to the gradlew command.

This works nicely for projects that distribute their source code via any of the version control systems that we will be discussing later.

2 gradle by example

A gradle project is controlled by two build files

settings.gradle in the project root directory gives project-wide info
- name and version of the project
- names of any subproject directories
build.gradle, in each subproject directory, desctibes the tasks for that subproject

I’ll work through a progressive series of builds for this project.

2.1 Simple Java Build

Using the Java plugin, a basic build with unit tests is easy:

settings.gradle

// A simple Java project

This file needs to exist, but can be empty.

build.gradle

plugins {
   id 'java'  ➀
}

repositories { ➁
    jcenter()
}

➀ This loads and runs the Java plugin.
- As long as our source code is arranged in the Apache/Android directory style, it will be handled correctly.
➁ The repositories section loads from JCenter (the default). Even this could probably be omitted in this build.

This is all you need to compile Java code stores in src/main/java.

2.2 Java Build with Third-Party Libraries

plugins {
   id 'java'
}

repositories {
    jcenter()
}

dependencies {
    implementation 'com.opencsv:opencsv:5.1'
    implementation 'commons-io:commons-io:2.6'
}

2.3 Java Build with Unit Tests

If you have unit tests, we need to add a little more info.

build.gradle

plugins {
   id 'java'
}

repositories {
    jcenter()
}

dependencies {
    implementation 'com.opencsv:opencsv:5.1'
    implementation 'commons-io:commons-io:2.6'
    testCompile 'org.junit.jupiter:junit-jupiter-api:5.6.1' ➀
    testRuntime 'org.junit.jupiter:junit-jupiter-engine:5.6.1' ➁
}

test {  ➂
    ignoreFailures = true ➃
    useJUnitPlatform()
}

The two sections at the end establish that

➀ When compiling our unit tests, we need to have the JUnit library available.

➁ When running our unit tests, we need the library junit-vintage-engine available.

➂ The code in the src/test directory contains our JUnit tests.

➃ Don’t stop the build just because we fail some tests.

➀ Add the plugin (this one by me)

➁ set the URLs for accessing and deploying the website.. Example is here.

2.4 C++ Multi-project Build

A multi-project build in gradle is kept in a directory tree.

The top-most directory is the master project.
- It contains the settings.gradle file.
Each subproject directory contains its own build.gradle file.

2.4.1 The master project

Any multi-project build in Gradle uses the settings.gradle file (usually in the common root containing the subproject directories) to identify the subprojects:

rootProject.name = 'manhattan'

include "application", "geomlib"

In this case, we have two subprojects. One provides the executable, the other a library of ADTs, with unit tests, constituting the bulk of the code design.

There is no need for build.gradle file at this level, although it would be legal to provide one if you have project-level steps to be carried out.

2.4.2 The geomlib subproject

Of the two subprojects, the geomlib subproject is probably most interesting because it does the most. It compiles code into a library, then compiles and runs unit tests on that library code. By contrast, the application subproject only compiles code.

Here is the build.gradle file for the lib subproject:

build.gradle.lib.listing

plugins {
    id 'cpp-library'
	id 'cpp-unit-test'
}


unitTest {
    binaries.whenElementKnown(CppTestExecutable) { binary ->
        if (binary.targetMachine.operatingSystemFamily.linux) {
            binary.linkTask.get().linkerArgs.add('-pthread')
        }
    }
}

This listing starts off with two plugins, one for C++ compilation (into a reusable library) and the other for unit testing.
The unit test plugin can work with a variety of frameworks. Eventually, you should be able to load these frameworks as dependencies, much as you do in Java projects.

In this case, I am using CppUnitLite because it can be easily dropped into the directory with the unit tests.
Like most unit test frameworks, this one runs the tests in a separate thread (process). The unittest configuration here adds the required pthread library when compiling under Linux.

2.4.3 The application subproject

The application subproject is simpler, because it only has one job to do – create an executable. Here it is:

build.gradle.exe.listing

plugins {
		id 'cpp-application'
}

dependencies {
			implementation  project(':geomlib')
}

Very simple: we invoke the cpp-application plugin and
Indicate that this depends on the :geomlib subproject
This dependency guarantees that the geomlib library will be constructed before this application is built and that it will be automatically included into the application compilation and link steps.

You can find this entire project, with the Gradle files, here.

3 Customizing Tasks

The gradle build files are Groovy scripts, with Java-like syntax. Many of the more common Java API packages are imported automatically.

task upper {
    doLast {
       String myName = "Steven Zeil";
       println myName;
       println myName.toUpperCase();
    }
}

If this is placed in build.gradle, then we can run it:

$ gradle upper
:upper
Steven Zeil
STEVEN ZEIL

BUILD SUCCESSFUL

Total time: 1.747 secs
$

3.1 Gradle Tasks

The basic elements of a Gradle build file are tasks.

Gradle tasks can correspond Ant targets.

A Gradle task can perform multiple actions.

task upper {
   doLast {
       String myName = "Steven Zeil";
       println myName;
       println myName.toUpperCase();
   }
}

Gradle tasks can correspond individual Ant tasks.

A Gradle task can perform multiple actions.
```
task copyResources (type: Copy) {
   from(file('src/main/resources'))
   into(file('target/classes'))
}
```
In Ant, we would have used a <copy> task within a larger Ant target for this purpose.

3.2 Anatomy of a Task

3.2.1 The phases of a Gradle run

Before looking at the components of a task, we need to understand a bit about how Gradle works.

A Gradle run occurs in four specific phases.

Initialization takes care of things that affect how Gradle itself will run. The most visible activity during this phase is loading Gradle plugins that add new behaviors.
Configuration involves collecting the build’s tasks, setting the properties of those tasks, and then deciding which tasks need to be executed and the order in which that will be done.
Execution is when the tasks that need to be executed get run.
Finalization covers any needed cleanup before the Gradle run ends.

3.2.2 Declaring tasks

A Gradle task can be declared as easily as:

task myTask

A Groovy function with parameters, e.g.,

void foo (int x, int y, int z) { ... }

can be called using positional arguments:

foo (12, 14, 0)

or by using named arguments:

foo (z: 0, x: 12, y: 14)

One advantage of the latter form is that you don’t have to know the order in which the parameters appeared in the function declaration. The named form is even more useful when all or most of the parameters have default values and, in your call, you only want to supply the value to one or two parameters for which you don’t like the defaults.

Some tasks may need parameters:

task copyResources (type: copy)

3.2.3 Configuring tasks

You can add code to be run at configuration time by putting it in { } brackets just after the task name:

task copyResources (type: Copy)

copyResources {
    description = 'Copy resources into a directory from which they will be added to the Jar'
    from(file('src/main/resources'))
    into(file('target/classes'))
}

You can combine a configuration with the task declaration:

task copyResources (type: Copy) {
    description = 'Copy resources into a directory from which they will be added to the Jar'
    from(file('src/main/resources'))
    into(file('target/classes'))
}

3.2.4 Executable Behavior

Task types often have pre-defined behaviors.
- For example, the Copy type copies files at execution time
```
task copyResources (type: Copy) {
    from(file('src/main/resources'))
    into(file('target/classes'))
}
```
  The from and into calls are performed at configuration time.
  
  The Copytype actually copies the files at execution time.
  - gradle will check to see, at configuration time, if the files already exist at the destination and appear to be no olderthan the ones at the source. If so, the copyResources task will be skipped at execution time.

3.2.5 Adding Executable Behavior

You can add code to be run at execution time by attaching it, within { }, using the doLast operation.

task copyResources (type: Copy) {
    from(file('src/main/resources'))
    into(file('target/classes'))
    doLast {
       println 'Copy has been done.'
    }
}

or you can use that operation to add the code to an already-declared task object.

task copyResources (type: Copy) {
    from(file('src/main/resources'))
    into(file('target/classes'))
}
⋮
copyResources.doLast {
    println 'Copy has been done.'
}

3.3 Task Dependencies

task setupFormat

task setupGraphics

task setupSourceCode


task generatePDFs (dependsOn: 'setup')
generatePDFs.doLast {  ➀
    println 'in task generatePDFs'
}

task setup (dependsOn: ['setupFormat',
                        'setupGraphics',
                        'setupSourceCode'])
setup.doLast {  ➁
   println 'in task setup'
}

task deploy (dependsOn: generatePDFs)
deploy.doLast {
    println 'in task deploy'
}

➀ : This line shows a dependency. Note that the task on which we are depending has not been declared yet.
➁ : The [a, b, ...] notation introduces a Groovy array value.