Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Update the pdf of the online documentation and commit it
  • create a temporary release branch and change to it

    Code Block
    git branch release
    git checkout release
  • Change the release version information

    No Format
          groovyVersion = 1.8.9
          groovyBundleVersion = 1.8.9
          groovyVersion = 1.8.9
          groovyBundleVersion = 1.8.9
  • commit the change
  • Tag with that new release

    Code Block
      git tag -a GROOVY_1_8_9 -m "tagging release of Groovy 1.8.9"
  • Build zips and jars using:

    Code Block
    ant clean dist

    You may need to set ANT_OPTS=-Xmx512m (or similar) if you run out of memory when running GroovyDoc.

  • Upload all the zips (but not jars) to the WebDAV distribution site (, for example, or through rsync if you're authorized:

    Code Block
    rsync -vlogDrzP ./target/dist/*.zip $

    (just check they are in the right place afterwards; you may still need a webdav client to move them into the right subdirectories if something goes wrong)

  • Put m2 jars into right place for uptake into repo1 (see Publishing artifacts on Building Groovy from Sourcefor more details):

    Code Block
    ant -DskipTests=true deploy

    If releasing Groovy 1.6, also do this:

    Code Block
    ant -DskipTests=true -DforceRetro=true -Djdk14home=... deploy    // for jdk14 artifacts also

    (Note 1: there is currently some duplicated work done by 'ant dist' above and 'ant deploy' here which we need to eventually consolidate)
    Should there be a problem when uploading the jars, check that there is a file ~/.m2/settings.xml containing:

    Code Block
    <?xml version="1.0"?>

    Where USER and PASSWORD are replaced if the right values.

  • Upload the javadocs through rsync to the WebDAV web site (, for example:

    Code Block
    rsync -vlogDrzP ./target/html/* $
  • remove the release branch and push the release tag

    Code Block
    git checkout <branch you released from>
    git branch -D release
    git push --tags
  • advance the version in your branch in pom.xml, and (don't forget the -SNAPSHOT)
  • Update the download links:
  • Update the versions.json file in through webdav to add a reference to the new version, so that GVM can automatically pickup new releases

    Code Block
            "version": "2.1.1",
            "link": "",
            "type": "final",
            "default": true
  • Announce the release (mailing-list, Groovy blog, twitter, Google+...)
  • Update the release version information to the next snapshot