Page History

...

#!/bin/sh
 
rel=$1
 
if [ -z "$rel" ]; then
  echo usage: $0 release
  exit 1
fi
 
exts="tar.gz tar.bz2 zip"
if [ -f "$rel.exe" ]; then
  exts="$exts exe"
fi
 
for i in $exts; do md5sum $rel.$i | sed 's/ .*$//g' >$rel.$i.md5; done
 
for i in $exts; do gpg --armor --output $rel.$i.asc --detach-sig $rel.$i; done

Put all the archives created by the assembly plugin in a separate directory and:

./sign-release.sh maven-2.0.2-bin
scp * people.apache.org:/www/www.apache.org/dist/maven/binaries

You can check the apache mirrors to see when content was last pulled by the mirrors: http://www.apache.org/mirrors/

• Announced RC.
• Moved RC binaries to release download area next morning
• mvn clean install release:prepare release:perform at components/maven-artifact-ant/pom.xml level.
• mvn clean assembly:assembly...SUCCESS
• Signed and uploaded binaries to release download area
• mvn clean install release:prepare release:perform at components/maven-embedder/pom.xml level.
• mvn clean assembly:assembly...SUCCESS
• Signed and uploaded binaries to release download area
• Updated website files to reflect 2.0.1 release:
• site/src/site/apt/download.apt
• site/src/site/xdoc/index.xml
• Performed mvn site site:deploy at site/pom.xml level.
• mvn -DperformRelease=true -N deploy at plugins/pom.xml level.
• NOTE: It seems that the release plugin doesn't like the -N switch...it will iterate over all modules anyway.