The Groovy Plugin

The Groovy plugin extends the Java plugin to add support for Groovy projects. It can deal with Groovy code, mixed Groovy and Java code, and even pure Java code (although we don’t necessarily recommend to use it for the latter). The plugin supports joint compilation, which allows you to freely mix and match Groovy and Java code, with dependencies in both directions. For example, a Groovy class can extend a Java class that in turn extends a Groovy class. This makes it possible to use the best language for the job, and to rewrite any class in the other language if needed.


To use the Groovy plugin, include the following in your build script:

Example 444. Using the Groovy plugin


apply plugin: 'groovy'


The Groovy plugin adds the following tasks to the project.

Table 51. Groovy plugin - tasks

Task name Depends on Type Description




Compiles production Groovy source files.




Compiles test Groovy source files.




Compiles the given source set’s Groovy source files.




Generates API documentation for the production Groovy source files.

The Groovy plugin adds the following dependencies to tasks added by the Java plugin.

Table 52. Groovy plugin - additional task dependencies

Task name Depends on







Figure 17. Groovy plugin - tasks

Groovy plugin - tasks

Project layout

The Groovy plugin assumes the project layout shown in Table 53. All the Groovy source directories can contain Groovy and Java code. The Java source directories may only contain Java source code.[22] None of these directories need to exist or have anything in them; the Groovy plugin will simply compile whatever it finds.

Table 53. Groovy plugin - project layout

Directory Meaning


Production Java source


Production resources


Production Groovy sources. May also contain Java sources for joint compilation.


Test Java source


Test resources


Test Groovy sources. May also contain Java sources for joint compilation.


Java source for the given source set


Resources for the given source set


Groovy sources for the given source set. May also contain Java sources for joint compilation.

Changing the project layout

Just like the Java plugin, the Groovy plugin allows you to configure custom locations for Groovy production and test sources.

Example 445. Custom Groovy source layout


sourceSets {
    main {
        groovy {
            srcDirs = ['src/groovy']

    test {
        groovy {
            srcDirs = ['test/groovy']

Dependency management

Because Gradle’s build language is based on Groovy, and parts of Gradle are implemented in Groovy, Gradle already ships with a Groovy library. Nevertheless, Groovy projects need to explicitly declare a Groovy dependency. This dependency will then be used on compile and runtime class paths. It will also be used to get hold of the Groovy compiler and Groovydoc tool, respectively.

If Groovy is used for production code, the Groovy dependency should be added to the compile configuration:

Example 446. Configuration of Groovy dependency


repositories {

dependencies {
    compile 'org.codehaus.groovy:groovy-all:2.4.10'

If Groovy is only used for test code, the Groovy dependency should be added to the testCompile configuration:

Example 447. Configuration of Groovy test dependency


dependencies {
    testCompile 'org.codehaus.groovy:groovy-all:2.4.10'

To use the Groovy library that ships with Gradle, declare a localGroovy() dependency. Note that different Gradle versions ship with different Groovy versions; as such, using localGroovy() is less safe then declaring a regular Groovy dependency.

Example 448. Configuration of bundled Groovy dependency


dependencies {
    compile localGroovy()

The Groovy library doesn’t necessarily have to come from a remote repository. It could also come from a local lib directory, perhaps checked in to source control:

Example 449. Configuration of Groovy file dependency


repositories {
    flatDir { dirs 'lib' }

dependencies {
    compile module('org.codehaus.groovy:groovy:2.4.10') {
        module('org.apache.ant:ant:1.9.4') {

Automatic configuration of groovyClasspath

The GroovyCompile and Groovydoc tasks consume Groovy code in two ways: on their classpath, and on their groovyClasspath. The former is used to locate classes referenced by the source code, and will typically contain the Groovy library along with other libraries. The latter is used to load and execute the Groovy compiler and Groovydoc tool, respectively, and should only contain the Groovy library and its dependencies.

Unless a task’s groovyClasspath is configured explicitly, the Groovy (base) plugin will try to infer it from the task’s classpath. This is done as follows:

  • If a groovy-all(-indy) Jar is found on classpath, that jar will be added to groovyClasspath.

  • If a groovy(-indy) jar is found on classpath, and the project has at least one repository declared, a corresponding groovy(-indy) repository dependency will be added to groovyClasspath.

  • Otherwise, execution of the task will fail with a message saying that groovyClasspath could not be inferred.

Note that the “-indy” variation of each jar refers to the version with invokedynamic support.

Convention properties

The Groovy plugin does not add any convention properties to the project.

Source set properties

The Groovy plugin adds the following convention properties to each source set in the project. You can use these properties in your build script as though they were properties of the source set object.

Table 54. Groovy plugin - source set properties

Property name Type Default value Description


SourceDirectorySet (read-only)

Not null

The Groovy source files of this source set. Contains all .groovy and .java files found in the Groovy source directories, and excludes all other types of files.


Set<File>. Can set using anything described in the section called “Specifying a set of input files”.


The source directories containing the Groovy source files of this source set. May also contain Java source files for joint compilation.


FileTree (read-only)

Not null

All Groovy source files of this source set. Contains only the .groovy files found in the Groovy source directories.

These properties are provided by a convention object of type GroovySourceSet.

The Groovy plugin also modifies some source set properties:

Table 55. Groovy plugin - source set properties

Property name Change


Adds all .java files found in the Groovy source directories.


Adds all source files found in the Groovy source directories.


The Groovy plugin adds a GroovyCompile task for each source set in the project. The task type extends the JavaCompile task (see the section called “CompileJava”). The GroovyCompile task supports most configuration options of the official Groovy compiler.

Table 56. Groovy plugin - GroovyCompile properties

Task Property Type Default Value





FileTree. Can set using anything described in the section called “Specifying a set of input files”.







groovy configuration if non-empty; Groovy library found on classpath otherwise

Compiling and testing for Java 6 or Java 7

The Groovy compiler will always be executed with the same version of Java that was used to start Gradle. You should set sourceCompatibility and targetCompatibility to 1.6 or 1.7. If you also have Java sources, you can follow the same steps as for the Java plugin to ensure the correct Java compiler is used.

Example 450. Configure Java 6 build for Groovy

# in $HOME/.gradle/


sourceCompatibility = 1.6
targetCompatibility = 1.6

assert hasProperty('java6Home') : "Set the property 'java6Home' in your your pointing to a Java 6 installation"
def javaExecutablesPath = new File(java6Home, 'bin')
def javaExecutables = [:].withDefault { execName ->
    def executable = new File(javaExecutablesPath, execName)
    assert executable.exists() : "There is no ${execName} executable in ${javaExecutablesPath}"
tasks.withType(AbstractCompile) {
    options.with {
        fork = true
        forkOptions.javaHome = file(java6Home)
tasks.withType(Javadoc) {
    executable = javaExecutables.javadoc
tasks.withType(Test) {
    executable =
tasks.withType(JavaExec) {
    executable =

[22] We are using the same conventions as introduced by Russel Winder’s Gant tool (