Mirror of Apache Groovy
Java Groovy GAP HTML CSS Shell Other
Failed to load latest commit information.
benchmark Added a compiler performance test module Sep 21, 2015
buildSrc Minor spelling and grammar fixes. (closes #117) Sep 13, 2015
config Remove incubator from the URL of the repositories (closes #202) Dec 2, 2015
gradle rename a property to better reflect reality (missed one instance in m… Jan 13, 2017
licenses L&N tweaks: typos and cosmetics Jul 23, 2015
notices Change end year in various notices (using updateNotices task) Jan 3, 2017
security Security Test fix - add permissions required to run under indy Jul 4, 2016
src GROOVY-8033: spread property calls on non-list collections fail STC i… Jan 9, 2017
subprojects minor cleanup and refactoring (closes #477) Jan 15, 2017
xdocs/images Remove the Maven 1 build files since we have now officially moved to … May 22, 2007
.gitignore use global gitignores instead of listing all subprojects individually… Feb 11, 2016
.travis.yml Travis CI - run with latest JDK8 (closes #364) Jul 9, 2016
DOAP.rdf Adding Apache Groovy DOAP file (closes #223) Dec 23, 2015
LICENSE GROOVY-7567: groovysh: Fix file completion with blanks, use escaping … Sep 1, 2015
NOTICE Change end year in various notices (using updateNotices task) Jan 3, 2017
README.adoc dummy commit, closes #357 Jun 30, 2016
build.gradle rename a property to better reflect reality Jan 10, 2017
gradle.properties mostly javac setup fixes for jdk9 Jul 16, 2016
gradlew use final version of gradle 3.0 Aug 22, 2016
gradlew.bat use final version of gradle 3.0 Aug 22, 2016
settings.gradle remove 1.7 checks from build files Sep 9, 2016


Apache Groovy


Groovy is a powerful, optionally typed and dynamic language, with static-typing and static compilation capabilities, for the Java platform aimed at multiplying developers’ productivity thanks to a concise, familiar and easy to learn syntax.

It integrates smoothly with any Java program, and immediately delivers to your application powerful features, including scripting capabilities, Domain-Specific Language authoring, runtime and compile-time meta-programming and functional programming.


Latest Groovy version is available on Bintray Bintray latest version

Binary distribution links are on the package page.

Maven, Gradle and Ivy dependency declaration snippets are available on specific files of a particular module.

Get automatic notifications about new

Obtaining the Source

You don’t need the source code to use Apache Groovy but if you wish to explore its inner workings or build it for yourself there are two ways to obtain the source files.

Checking out from Version Control

Apache Groovy uses Git. The official Git repository is at:


And a mirror is hosted on Github:


The Github mirror is read-only and provides convenience to users and developers to explore the code and for the community to accept contributions via Github pull requests.

Simply git clone the repo (or the repo you forked via the github website) and you will have the complete source.

Unpacking the src distribution

Alternatively, you can download the source distribution and unpack it.

If obtaining the source from this distribution and you intend to build from source, you also need to download and install Gradle and execute one bootstrap step. At the top directory of your unpacked source, you need to run the command:


This sets up the Gradle wrapper and from then on you just need the gradlew command instead of gradle.

Building from Source

Build is build status.

To build you will need:

To build everything using Gradle:

gradlew clean dist

Note: The gradlew command automatically downloads the correct Gradle version if needed, you do not need to download it first.

This will generate a distribution similar to the zip you can download on the Groovy download page.

To build everything and launch unit tests, use:

gradlew test

If you want to launch one unit test, use this. <TestClassName> is like groovy.GroovyMethodsTest.

gradlew :test --tests <TestClassName>

To build from IntelliJ IDEA:

gradlew jar idea

Then open the generated project in IDEA.

To build from Eclipse:

gradlew jar eclipse

Then open the generated project and the generated subprojects in Eclipse. But be aware that Eclipse tends to be more limited in its ability to reproduce a Gradle build structure. The generated project files may contain a circular dependency which may or may not prevent Eclipse from using them. It depends on the Eclipse version, if this is an issue or not.

To build the documentation (Groovy Language Documentation):

gradlew assembleAsciidoc

All code samples of the documentation guide are pulled from actual test cases. To run a single documentation test case, take for example src/spec/test/semantics/PowerAssertTest.groovy

gradlew testSinglePowerAssertTest

(Note the omission of package name: class is semantics.PowerAssertTest but only PowerAssertTest is added to testSingle.)

InvokeDynamic support

The Groovy build supports the JVM instruction invokedynamic. If you want to build Groovy with invokedynamic, you can use the project property indy:

gradlew -Pindy=true clean test

Please note that the following Gradle tasks generate both indy and non indy variants of the jars, so you don’t need to use the system property:

  • dist

  • install

  • uploadArchives

Continuous Integration Server

The official CI server runs here and is sponsored by JetBrains.


Groovy is licensed under the terms of the Apache License, Version 2.0