THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Release Process Notes for Maven 2.0.2
- moved benchmark to the sandbox
- moved examples to the sandbox
- it would be nice to separate the stuff that is really the core from the
- integration tests
- the ant bindings (depends on the core)
- the embedder (depends on the core)
- the ant and embedder build should be similar, using a property to control the version, these two builds
need to be grouped together due their similarity - i changed the release plugin so that we have an up-front check for snapshot dependencies in the projects in the reactor and
to make sure there are no non-snapshot version numbers. - in the top level directory of the 2.0.x branch: mvn release:prepare
- maven-meeper should be moved out of the core, snapshots still remain as not in modules list
- maven-repository-tools should be moved out of the core, snapshots still remain as not in modules list
- we should build the release using 1.4.x of the JVM
- in the top level directory of the 2.0.x branch: mvn release:perform
- mvn clean assembly:assembly from components/maven-core/pom.xml level
- Signed and uploaded
#!/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.