Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2007-08-08 00:01:27 →
Size: 1047
Editor: ElliotMetsger
Comment:
← Revision 4 as of 2009-09-20 23:46:30 → ⇥
Size: 1049
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
To publish Maven 2 artifacts, simply copy the artifacts from the staging repository to the production repository. See [http://wiki.apache.org/portals/Pluto/CuttingRelease/ServerLocations]. To publish Maven 2 artifacts, simply copy the artifacts from the staging repository to the production repository. See [[http://wiki.apache.org/portals/Pluto/CuttingRelease/ServerLocations]].

Publishing Maven 2 Artifacts

To publish Maven 2 artifacts, simply copy the artifacts from the staging repository to the production repository. See http://wiki.apache.org/portals/Pluto/CuttingRelease/ServerLocations.

I normally use rsync to move the files, which makes things pretty easy.

  • Use the -nv arguments to see a list of files to be moved.

  • Use the -c argument to move files based on checksum instead of timestamps or other file metadata.

  • Use -a to include subdirectories.

  • Use --exclude *SNAPSHOT* to not copy SNAPSHOT versions.

  • Do not forget the trailing slashes on the source and destination. 

rsync -n -vac --exclude *SNAPSHOT*
/www/people.apache.org/builds/portals-pluto/m2-staging-repository/org/apache/pluto/ /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/pluto/

Remove -n from the above command to actually perform the rsync and publish the Maven 2 artifacts from the staging repository to the production repository.

Pluto/CuttingRelease/PublishMaven2Artifacts (last edited 2009-09-20 23:46:30 by localhost)