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 68 Next »

Instructions (for 2.0+ releases)

JDK 7 mandatory

Icon

Make sure you are using a Java 7 JDK, otherwise Groovy would be compiled without invoke dynamic support

  • Update the pdf of the online documentation and commit it
  • perform a clean checkout into a new, empty directory

  • create a temporary release branch and change to it

  • Change the release version information

  • commit the change

  • Tag with that new release

  • Test the release

If everything passes, proceed to the next step. Otherwise, release is not possible and problems should be fixed first.

  • Build zips and jars using:

 

  • Upload all the zips (but not jars) to the WebDAV distribution site (https://dav.codehaus.org/dist/groovy/distributions), 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)

  • Upload the javadocs through rsync to the WebDAV web site (https://dav.codehaus.org/groovy/), for example:

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

    Prior to uploading, you must make sure you have rights to upload artifacts to the CodeHaus repository. If so, you must have two system properties set before uploading:

    Then you may upload artifacts using the following command (note there are lots of artifacts to upload, do not be surprised if it takes more than an hour):

    Or with the user / password passed as properties:

    Should there be 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.

  • If you are affected by authentication issues, due to the odd certificates used by Codehaus, and if the installation of those certificates are problematic on your machine (if the certificates are rejected or if you're not running as root, etc), you can use a local keystore:

  • remove the release branch and push the release tag

  • advance the version in your branch in gradle.properties (don't forget the -SNAPSHOT)
  • Update the download links: http://docs.codehaus.org/display/GROOVY/Download
  • Update the versions.json file in http://dist.groovy.codehaus.org/ through webdav to add a reference to the new version, so that GVM can automatically pickup new releases

  • Announce the release (mailing-list, Groovy blog, twitter, Google+...)
  • Update the release version information to the next snapshot

if the certificate needs an update see: https://docs.codehaus.org/display/HAUSMATES/Installing+a+new+CA+into+the+JDK

Instructions (for pre-2.0 releases)

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

  • Change the release version information

    "files"
      ./build.properties:
          groovyVersion = 1.8.9
          groovyBundleVersion = 1.8.9
      ./gradle.properties:
          groovyVersion = 1.8.9
          groovyBundleVersion = 1.8.9
      .pom.xml:
          <version>1.8.9</version>
    
  • commit the change
  • 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 (https://dav.codehaus.org/dist/groovy/distributions), 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 Sourcefor more details):

    If releasing Groovy 1.6, also do this:

    (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:

    Where USER and PASSWORD are replaced if the right values.

  • Upload the javadocs through rsync to the WebDAV web site (https://dav.codehaus.org/groovy/), for example:

  • remove the release branch and push the release tag

  • advance the version in your branch in pom.xml, build.properties and gradle.properties (don't forget the -SNAPSHOT)
  • Update the download links: http://docs.codehaus.org/display/GROOVY/Download

  • Announce the release (mailing-list, Groovy blog, twitter, Google+...)
  • Update the release version information to the next snapshot

if the certificate needs an update see: https://docs.codehaus.org/display/HAUSMATES/Installing+a+new+CA+into+the+JDK

  • No labels