Page History

...

• artifacts for each and every release must be SIGNED; your public key should be added to the KEYS file
• your public key must also be cross-signed by other Apache committers (this can be done at key signing parties at ApacheCon for instance)
• make sure you have the correct maven configuration in ~/.m2/settings.xml
• use Maven 2.2.1+ (Maven 2.1.x is known to produce wrong gpg pom signatures - MGPG-14)
  • from Camel 2.10 onwards we will require to use Maven 3.0.x+
• you may want to get familiar with the release settings in the parent apache POM.
• make sure you have installed princexml to be able to generate the Camel manual
  • Add the bin directory to your path variable

    Code Block
    PATH=$PATH:/usr/local/lib/prince/bin

Maven 2 Setup

Before you deploy anything to the maven repository using Maven 2, you should configure your ~/.m2/settings.xml file so that the file permissions of the deployed artifacts are group writable. If you do not do this, other developers will not able to overwrite your SNAPSHOT releases with newer versions. The settings follow the guidelines used by the Maven project. Please pay particular attention to the password encryption recommendations.

...