Page History

...

To deploy a snapshot (Apache committers only), run

mvn -Pdeploy deploy

That will deploy the latest snapshot along with the javadoc and source jar bundles to apaches snapshot repository. After deploying the snapshot, you need to login to people.apache.org and fix the permissions. cd to /www/people.apache.org/repo/m2-snapshot-repository and run the fix-permissions.sh script.

...

1. Run with extra flags to skip the code checks and running of the tests

   Code Blocknoformat
   mvn -Pdeploy,nochecks deploy -Dmaven.test.skip.exec=true

2. HIGHLY RECOMMENDED: use a "Master Mode" ssh connection to people.apache.org for the scp commands to use. This requires a fairly recent version of ssh. Basically, in your ~/.ssh/config, make sure you have "ControlPath /tmp/%h-%p-%r" set. Then, in one window, run "ssh -Mv people.apache.org". Then run the deploy in another. The -v on the ssh connection will print things for each connection so you'll know it working. This is MUCH faster as SCP doesn't need to negotiate encryption stuff for every single file, doesn't need to open up lots of connections, etc....

If your user name on people.apache.org is not the same as your user name on your home system, you will need to add some configuration to your ~/.m2/settings.xml. The following works on the assumption that you've published your ssh
public key to people.apache.org.

<settings>
  <servers>
    <server>
      <id>apache.releases</id>
      <username>bimargulies</username>
    </server>
    <server>
      <id>apache.snapshots</id>
      <username>bimargulies</username>
    </server>
  </servers>
<settings>

...

After that is setup, you need to update the release_notes.txt in the distribution/src/main/release, and run the below commands.

mvn release:prepare -Peverything
mvn release:perform

...