Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Docs upload must be processed before artifactsUpload otherwise the html directory is missing

...

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

    Code Block
    rsync -vlogDrzP ./target/dist/*.zip $USER@groovy.codehaus.org:/projects/groovy/dist/
    

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

    Code Block
    rsync -vlogDrzP ./target/html/* $USER@groovy.codehaus.org:/projects/groovy/web/
  • 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:

    Code Block
    groovy.deploy.username
    groovy.deploy.password

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

    Code Block
    ./gradlew clean uploadArchives
    

    Or with the user / password passed as properties:

    Code Block
    ./gradlew -Dgroovy.deploy.username=USER -Dgroovy.deploy.password=PASSWORD clean uploadArchives

    Should there be a problem when uploading the jars, check that there is a file ~/.m2/settings.xml containing:

    Code Block
    XML
    XML
    <?xml version="1.0"?>
    <settings>
      <servers>
        <server>
          <id>codehaus.org</id>
          <username>USER</username>
          <password>PASSWORD</password>
        </server>
      </servers>
    </settings>
    

    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:

    Code Block
    rsync -vlogDrzP ./target/html/* $USER@groovy.codehaus.org:/projects/groovy/web/
    
  • 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 gradle.properties (don't forget the -SNAPSHOT)
  • Update the download links: http://docs.codehaus.org/display/GROOVY/Download
  • Announce the release
  • Update the release version information to the next snapshot

...