Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 49 Next »


  • Update the pdf of the online documentation and commit it
  • create a temporary release branch and change to it
  • Change the release version information
          groovyVersion = 1.9-beta-3
          groovyBundleVersion = 1.9-beta-3
  • Tag with that new release
  • Build zips and jars using:
    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:
    (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 Source for more details):
    (Note 1: there is currently some duplicated work done by 'ant dist' above and 'ant deploy' here which we need to eventually consolidate)
    Should therebe a problem when uploading the jars, check that there is a file ~/.m2/settings.xml containing:
    Where USER and PASSWORD are replaced if the right values.
  • Upload the javadocs through rsync to the WebDAV web site (, for example:
  • remove the release branch and push the release tag
  • advance the version in your branch in pom.xml and (don't forget the -SNAPSHOT)
  • Update the download links:
  • Announce the release
  • Update the release version information to the next snapshot

if the certificate needs an update see:

  • No labels