This plugin adds Groovy language support for Android applications and libraries.

Use a lazybones template from grooid-template

Edit your build.gradle file with the following:

The latest version can be found here

Then you must choose which version of Groovy you use. So far, Android support is available in the 2.4.0 release and beyond, you will need to add the following repository to your build.gradle file:

Then you can start using Groovy by adding the groovy dependency with the grooid classifier:

where $groovyVersion should be released with a version from here. Then use the assembleDebug task to test out your build and make sure everything compiles.

Should you want to test development versions of the plugin, you can add the snapshot repository and depend on a SNAPSHOT:

Go here to see what the latest SNAPSHOT version is.

Groovy sources may be placed in src/main/groovy, src/test/groovy, src/androidTest/groovy and any src/${buildVariant}/groovy configured by default. A default project will have the release and debug variants but these can be configured with build types and flavors. See the android plugin docs for more about configuring different build variants.

Extra groovy sources may be added in a similar fashion as the android plugin using the androidGroovy.sourceSets block. This is especially useful for sharing code between the different test types, and also allows you to add Groovy to a previous project. For example

would add all of the Java files in src/main/java directory to the Groovy compile task. These files will be removed from the Java compile task, instead being compiled by the Groovy compile, and will allow for the Java sources to make references to the Groovy sources (joint compilation). Please note, that you may need to also add these extra directories to the Java source sets in the android plugin for Android Studio to recognize the Groovy files as source.

This plugin has been successfully tested with Android Studio and will make no attempts to add support for other IDEs. This plugin will let you write an application in Groovy but it is recommended, for performance, memory and battery life, that you use @CompileStatic wherever possible.

Details can be found on Melix’s blog and here for more technical details

In order to include libraries written in groovy that include the groovy or groovy-all jars, you will need to exclude the groovy dependency allowing the grooid jar to be the one to be compiled against.

For example to use the groovy-xml library you would simply need to do exclude the group org.codehaus.groovy.

The Groovy compilation tasks can be configured in the androidGroovy block using the options block:

See GroovyCompile for more options. See Example Application for an example of using these settings to enable custom compilation options.

For integration with plain java projects or for working with generated files (such as BuildConfig) it may be desirable to only have GroovyC run in order to have Java files reference Groovy files. This is roughly the equivalent of placing all java source files into the groovy source directory (including auto generated files like BuildConfig). In order to only have GroovyC run simply set the flag skipJavaC in the androidGroovy block to true.

To use annotation processing javaAnnotationProcessing must be set to true in groovyOptions

A useful but not required tool is android-apt which helps android studio pick up generated files so that auto-complete works correctly.

For more examples of annotation processing setup see Example Dagger Application and Example Databinding Application

Databinding is actually annotation processing but hidden behind Android Studio and a Gradle plugin. Because of this you will need to use the android-apt in order to see any of the generated output files.

The setup for Databinding and Annotation Processing are the same, refer to the previous section in order to enable Annotation Processing.

Groovy Extension Modules and Global transformations both need a file descriptor in order to work. Android packaging has a restriction related to files having the same name located in the same path.

If you are using several Groovy libraries containing extension modules and/or global transformations, Android may complain about those files.

You can simply add the following rule:

There are no problems excluding global transformation descriptors because those are only used at compile time, never at runtime.

The problem comes with module extensions. Unless you statically compile classes using extension modules with @CompileStatic they won’t be available at runtime and you’ll get a runtime exception.

There is an alternative. The emerger gradle plugin will add excludes for you and merges all extension module descriptors into a single file which will be available at runtime.