Page History

...

4. Do another full build inside the source tarball. This time, allow all unit tests & integration tests to run and also include the docs

cd apache-flume-X.Y.Z
mvn clean install -Psite

Signatures and Checksums

All artifacts must be signed and checksummed. In order to sign a release you will need a PGP key. You should get your key signed by a few other people. You will also need to recv their keys from a public key server. See the Apache release signing page for more details.

...

2. Create and sign the artifacts, including site docs

From the flume root directory

mvn clean deploy -Psite -Psign -DskipTests

This will sign, hash, and upload each artifact to Nexus.

...

After you get your settings.xml file configured correctly (see above link) then you can run: mvn clean deploy -Psite -DskipTests -Papache-release to push the artifacts to the staging repo.
You will need to go to the Apache Maven Repository @ http://repository.apache.org/ and log in with your Apache LDAP credentials
Once you log in you will see Build Promotion > Staging Repositories on the left hand side
You will want to edit the Flume artifacts that you don't want to push to Maven (you can delete stuff like the release tarball)
Click Close to make the atrifacts available on the Staging repository.
To push to Central, you click Release.

...