mvn -e org.apache.rat:apache-rat-plugin:check
grep -e ' !?????' target/rat.txt -- will show any files without licenses
Info
Because of MRELEASE-812, you should use the following setting:
Code Block
language
text
LANG='en_US.UTF-8'
Do a release dry run to check for problems
Code Block
mvn release:prepare -DdryRun=true
Check that you are happy with the results. The poms for the proposed tags will be in pom.xml.tag. Check also the generated signature files:
Code Block
cmueller$ gpg camel-core/target/camel-core-2.7.5-SNAPSHOT.jar.asc
gpg: Signature made Tue Jan 10 20:50:27 2012 CET using RSA key ID 2A239C2C
gpg: Good signature from "Christian Mueller (CODE SIGNING KEY) <[email protected]>"
When you like the results, clean up:
Code Block
mvn release:clean
Prepare the release
Code Block
mvn release:prepare
This will create the tag in svn and leave various stuff around locally to direct the perform phase.
Info
Note: If you're located in Europe then release:prepare may fail with 'Unable to tag SCM' and 'svn: No such revision X'. Wait 10 seconds and run
Login to https://repository.apache.org using your Apache LDAP credentials. Click on "Staging Repositories". Then select "org.apache.camel-xxx" in the list of repositories, where xxx represents your username and ip. Click "Close" on the tool bar above. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything. Enter the name and version of the artifact being released in the "Description" field and then click "Close". This will make it easier to identify it later.
See the image in the original guide for more info.
If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If the you don't like the content of the repository, right click your repository and choose "Drop". You can then rollback your release and repeat the process. Note the repository URL, you will need this in your vote email.
Release Guide 