Sonatype OSS Maven Repository Usage Guide

快来打我* 2022-01-14 01:15 272阅读 0赞

原文：[https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide][https_docs.sonatype.org_display_Repository_Sonatype_OSS_Maven_Repository_Usage_Guide]

# [Sonatype OSS Maven Repository Usage Guide][https_docs.sonatype.org_display_Repository_Sonatype_OSS_Maven_Repository_Usage_Guide] #

*  
 *  [Attachments:4][Attachments_4]
 *  Added by [Juven Xu][], last edited by [Joel Orlina][] on Jun 05, 2013  ([view change][])

*  [1. Introduction][]
 *  [1a. Terms of Service][]
 *  [2. Sign up][]
 *  [3. Create a JIRA ticket][]
 *  [4. Maven Repositories][]
 *  [5. Prerequisites][]
 *  [6. Central Sync Requirement][]
 *  [7a. Deploy Snapshots and Stage Releases with Maven][]
    
     *  [7a.1. POM and settings config][]
     *  [7a.2. Publish Snapshots][]
     *  [7a.3. Stage a Release][]
 *  [7b. Stage Existing Artifacts][]
 *  [7c. Deploy Snapshots and Stage Releases with Ant][]
 *  [7d. Stage Releases with Gradle][]
 *  [7e. Deploy and Stage with SBT][]
 *  [8a. Release It][]
 *  [8b. Automating Releases][]
 *  [8c. Automating Releases in Nexus 2.4][]
 *  [9. Activate Central Sync][]
 *  [10. Help][]
 *  [11. What Do People Think About OSSRH][]

### 1. Introduction ###

Sonatype OSSRH (OSS Repository Hosting Service) uses [Nexus][] to provide Maven repository hosting service for open source projects: [https://oss.sonatype.org/][https_oss.sonatype.org]. You can deploy snapshots, stage releases, and promote your releases so they will be synced to [The Central Repository][]. All you need to do is to sign up a Sonatype JIRA account, create a JIRA ticket and make some POM/settings configuration. This document will guide you step by step for the details.

### [1a. Terms of Service][1a. Terms of Service 1] ###

### 2. Sign up ###

You need a Sonatype JIRA account to create tickets and access your Maven repositories. Go to [https://issues.sonatype.org/][https_issues.sonatype.org]

1.  Click the *Sign Up* link under the Username field.
2.  Fill in the Sign up form and submit.

![sign_up_1.png_version_1_modificationDate_1276583992178][]

![sign_up_2.png_version_1_modificationDate_1276584039405][]

### 3. Create a JIRA ticket ###

1.  Go to [Sonatype Open Source Project Repository Hosting JIRA][]
2.  Create a ticket with *Project* of **Support - Open Source Project Repository Hosting** and *Issue Type* of **New Project**
3.  Fill the page with the following information
    
    <table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; margin:5px 0px; border-collapse:collapse; padding:0px"> 
     <tbody> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> Summary</td> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> a brief introduction of your project</td> 
      </tr> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> groupId</td> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> <strong>IMPORTANT</strong>&nbsp;the groupId of your projects, generally it must match your domain name, so&nbsp;<em>com.googlecode.myprj</em>&nbsp;is valid but&nbsp;<em>myprj</em>&nbsp;is not, if you are unsure about this, please read&nbsp;<a href="https://docs.sonatype.org/display/Repository/Choosing+your+Coordinates" title="Choosing your Coordinates" style="color:rgb(0,51,102)" rel="nofollow">Choosing your Coordinates</a></td> 
      </tr> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> Project URL</td> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> location of the project website</td> 
      </tr> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> SCM URL</td> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> location of source control system</td> 
      </tr> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> Nexus Username</td> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> the JIRA Username you just signed up, one or more</td> 
      </tr> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> Already Sync To Central</td> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> are there any artifacts with same groupId existing in The Central Repository&nbsp;already?</td> 
      </tr> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> Description</td> 
       <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> any other information you think we need to know</td> 
      </tr> 
     </tbody> 
    </table>

After the ticket is created, we will prepare Maven repositories for you. We will update the ticket and set it as \_resolved\_ once it’s done. Normally it takes less than 2 business days.

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(221,255,221); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/check.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>How does a new user ask for publish rights to existing repositories</strong><br> Follow step 2, sign up and then leave a comment on the JIRA ticket with the username. We will assign related roles to him and update the ticket.</td> 
  </tr> 
 </tbody> 
</table>

### 4. Maven Repositories ###

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; margin:5px 0px; border-collapse:collapse; padding:0px"> 
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> <a href="https://oss.sonatype.org/content/repositories/snapshots/" style="color:rgb(0,51,102)" rel="nofollow">https://oss.sonatype.org/content/repositories/snapshots/</a></td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> repository for deploying snapshots</td> 
  </tr> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> <a href="https://oss.sonatype.org/service/local/staging/deploy/maven2/" style="color:rgb(0,51,102)" rel="nofollow">https://oss.sonatype.org/service/local/staging/deploy/maven2/</a></td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> repository for staging releases, you should never visit this url in browser</td> 
  </tr> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> <a href="https://oss.sonatype.org/content/repositories/releases/" style="color:rgb(0,51,102)" rel="nofollow">https://oss.sonatype.org/content/repositories/releases/</a></td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> repository where staging promotion will go, this repository is synced to&nbsp;<a href="http://repo1.maven.org/maven2/" style="color:rgb(0,51,102)" rel="nofollow">The Central Repository</a>, but you should not deploy to this repository directly</td> 
  </tr> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> <a href="https://oss.sonatype.org/content/groups/public/" style="color:rgb(0,51,102)" rel="nofollow">https://oss.sonatype.org/content/groups/public/</a></td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> repository group which contains snapshots and releases</td> 
  </tr> 
 </tbody> 
</table>

### 5. Prerequisites ###

*  JDK 5+ is installed on your command line path.
 *  Subversion 1.5+ is installed on your command line path. For more information, please refer to [http://subversion.apache.org/][http_subversion.apache.org].
 *  Maven 2.2.1+ is installed on your command line path.
    
    <table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(255,255,206); padding:0px 20px; width:1285px">     
     <tbody> 
      <tr style="font-size:10pt; line-height:13pt"> 
       <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt=""></td> 
       <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Note</strong><br> Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and checksums respectively.</td> 
      </tr> 
     </tbody> 
    </table>
 *  A GPG client is installed on your command line path. For more information, please refer to [http://www.gnupg.org/][http_www.gnupg.org].
 *  You have created your GPG keys and distributed your public key to hkp://pool.sks-keyservers.net/. For more information, please refer to [How To Generate PGP Signatures With Maven][].

### 6. Central Sync Requirement ###

To [Improve The Central Repository and the Supporting the Maven Ecosystem][], all artifacts to be synced to central must meet these requirements.

*  Project POM has the following elements.
    
     *  <modelVersion>
     *  <groupId>
     *  <artifactId>
     *  <version>
     *  <packaging>
     *  <name>
     *  <description>
     *  <url>
     *  <licenses>
     *  <scm><url>
     *  <scm><connection>
     *  <developers>
 *  If the project packaging is *jar*, and the jar file contains java classes, there must be a *-javadoc.jar* for main artifact.
 *  If the project packaging is *jar*, and the jar file contains java classes, there must be a *-sources.jar* for main artifact.
 *  All project artifacts are signed using GPG, and the public key is distributed to *hkp://pool.sks-keyservers.net/*. For more information, please refer to [How To Generate PGP Signatures With Maven][].

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(255,255,206); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Sources and Javadoc</strong><br> If, for some reason (for example, license issue or it's a Scala project), you can not provide -sources.jar or -javadoc.jar, please make fake -sources.jar or -javadoc.jar with simple README inside to pass the checking. We don't want to disable the rules because some people tend to skip it if they have an option.</td> 
  </tr> 
 </tbody> 
</table>

Some folks have asked why do we require all this information in the POM for deployed artifacts so here's a small explanation. The POM being deployed with the artifact is part of the process to make transitive dependencies a reality in Maven. The logic for getting transitive dependencies working is really not that hard, the problem is getting the data. The other applications that are made possible by having all the POMs available for artifacts are vast, so by placing them into the repository as part of the process we open up the doors to new ideas that involve unified access to projects.

We also ask for license now because it is possible that your project's license may change in the course of its life time and we are trying create tools to help normal people sort out licensing issues. For example, knowing all the licenses for a particular graph of artifacts we could have some strategies that would identify potential licensing problems.

Besides, we **discourage** putting release repository/pluginRepository in your POM. In ideal conditions, all your dependencies should be already in central and central repository is self-contained. Otherwise people's build might break because of missing dependencies. If some of your dependencies are not in central, please upload them using our [3rd-party artifacts bundle upload service][].

Brian has written 2 posts from different angles:

*  [Why Putting Repositories in your POMs is a Bad Idea][]
 *  [Why external repos are being phased out of Central][]

**a complete sample POM**

<project>
      <modelVersion>4.0.0</modelVersion>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven</artifactId>
      <packaging>jar</packaging>
      <name>Maven core</name>
      <version>2.0</version>
      <description>The maven main core project description</description>
      <url>http://maven.apache.org</url>
      <licenses>
        <license>
          <name>The Apache Software License, Version 2.0</name>
          <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
          <distribution>repo</distribution>
        </license>
      </licenses>
      <scm>
        <url>http://svn.apache.org/viewcvs.cgi/maven</url>
        <connection>http://svn.apache.org/viewcvs.cgi/maven</connection>
      </scm>
      <developers>
        <developer>
          <id>...</id>
          <name>...</name>
          <email>...</email>
        </developer>
      </developers>
      <dependencies>
        <dependency>
          <groupId>...</groupId>
          <artifactId>...</artifactId>
          <version>...</version>
        </dependency>
        ...
      </dependencies>
      
    </project>

### 7a. Deploy Snapshots and Stage Releases with Maven ###

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(255,255,206); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Note</strong><br> When deploying artifacts using Maven or any of the other methods below, there is currently a limit of roughly&nbsp;<strong>200MB</strong>&nbsp;on any&nbsp;<strong>single</strong>&nbsp;file uploaded to OSSRH. Your uploads will fail with a broken pipe exception when you hit this limit.</td> 
  </tr> 
 </tbody> 
</table>

#### 7a.1. POM and settings config ####

Configure your POM to inherit from [Sonatype OSS Parent POM][]:

<project>
      ...
      <parent>
        <groupId>org.sonatype.oss</groupId>
        <artifactId>oss-parent</artifactId>
        <version>7</version>
      </parent>
      ...
    </project>

Configure your POM's SCM element with the information matching your SCM repository like this:

**Subversion**

<project>
      ...
      <scm>
        <connection>scm:svn:http://foo.googlecode.com/svn/trunk/</connection>
        <developerConnection>scm:svn:https://foo.googlecode.com/svn/trunk/</developerConnection>
        <url>http://foo.googlecode.com/svn/trunk/</url>
      </scm>
      ...
    </project>

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(255,255,206); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Note</strong><br> If you don't use the&nbsp;<a href="http://svnbook.red-bean.com/en/1.5/svn.branchmerge.maint.html#svn.branchmerge.maint.layout" style="color:rgb(0,51,102)" rel="nofollow">standard svn layout</a>&nbsp;, you must configure&nbsp;<a href="http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#tagBase" style="color:rgb(0,51,102)" rel="nofollow">tagBase</a>&nbsp;of&nbsp;<a href="http://maven.apache.org/plugins/maven-release-plugin/" style="color:rgb(0,51,102)" rel="nofollow">maven-release-plugin</a>.</td> 
  </tr> 
 </tbody> 
</table>

**Git**

<project>
      ...
      <scm>
        <connection>scm:git:git@github.com:juven/git-demo.git</connection>
        <developerConnection>scm:git:git@github.com:juven/git-demo.git</developerConnection>
        <url>git@github.com:juven/git-demo.git</url>
      </scm>
      ...
    </project>

**Git hosted by Google Code**

<project>
      ...
      <scm>
        <connection>scm:git:https://code.google.com/p/foo/</connection>
        <developerConnection>scm:git:https://code.google.com/p/foo/</developerConnection>
        <url>http://code.google.com/p/foo/source/browse</url>
      </scm>
      ...
    </project>

**Mercurial**

<project>
      ...
      <scm>
        <connection>scm:hg:http://bitbucket.org/juven/hg-demo</connection>
        <developerConnection>scm:hg:https://bitbucket.org/juven/hg-demo</developerConnection>
        <url>http://bitbucket.org/juven/hg-demo</url>
      </scm>
      ...
    </project>

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(255,255,206); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Note</strong><br> You need to store your HTTP login so&nbsp;<strong>hg push</strong>&nbsp;won't ask for it from command line.<br> Edit&nbsp;<em>.hg/hgrc</em>&nbsp;like this: 
    <div style="padding:0px; margin:10px 20px; background-color:rgb(255,255,255); border:1px solid rgb(102,153,204); overflow:hidden"> 
     <div style="margin:0px; padding:12px 10px; font-size:0.95em"> 
      <pre style="padding:0px; margin-top:0px; margin-bottom:0px; overflow:auto; font-family:'Courier New',Courier,monospace; line-height:1.3">[auth]
hg-demo.prefix = https://bitbucket.org/juven/
hg-demo.username = juven
hg-demo.password = ******
</pre> 
     </div> 
    </div> </td> 
  </tr> 
 </tbody> 
</table>

Configure your Maven settings.xml, typically located in your ~/.m2 directory:

<settings>
      ...
      <servers>
        <server>
          <id>sonatype-nexus-snapshots</id>
          <username>your-jira-id</username>
          <password>your-jira-pwd</password>
        </server>
        <server>
          <id>sonatype-nexus-staging</id>
          <username>your-jira-id</username>
          <password>your-jira-pwd</password>
        </server>
      </servers>
      ...
    </settings>

#### 7a.2. Publish Snapshots ####

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(216,228,241); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/information.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Information</strong><br> 
    <ul style="font-size:10pt; line-height:13pt"> 
     <li style="font-size:10pt; line-height:13pt; margin:0px; padding:0px">Have no idea what a SNAPSHOT version is? The&nbsp;<a href="http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-pom-syntax.html" style="color:rgb(0,51,102)" rel="nofollow">POM Syntax</a>&nbsp;section of the book&nbsp;<a href="http://www.sonatype.com/books/mvnref-book/reference/" style="color:rgb(0,51,102)" rel="nofollow">Maven: The Complete Reference</a>&nbsp;is for you. We highly recommend this book if you are new to Maven.</li> 
     <li style="font-size:10pt; line-height:13pt; margin:0px; padding:0px">SNAPSHOT versions are NOT synchronized to Central. If you wish your users to consume your SNAPSHOT versions, they would need to add the snapshot repository to their Nexus, settings.xml, or pom.xml</li> 
     <li style="font-size:10pt; line-height:13pt; margin:0px; padding:0px">Successfully deployed SNAPSHOT versions will be found in&nbsp;<a href="https://oss.sonatype.org/content/repositories/snapshots/" style="color:rgb(0,51,102)" rel="nofollow">https://oss.sonatype.org/content/repositories/snapshots/</a></li> 
    </ul> </td> 
  </tr> 
 </tbody> 
</table>

To publish a snapshot, simply run:

$ mvn clean deploy

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(255,255,206); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Note</strong><br> If you experience a HTTP 401 error during deployment, make sure your settings.xml is correctly configured and you can log into Nexus UI using the server username/password. See&nbsp;<a href="http://www.sonatype.com/people/2010/11/what-to-do-when-nexus-returns-401/" style="color:rgb(0,51,102)" rel="nofollow">this blog</a>&nbsp;for more details in troubleshooting 401 errors during deployment.</td> 
  </tr> 
 </tbody> 
</table>

Don't worry about deploying too many snapshots so server disk will be overloaded. Nexus server has a scheduled task running weekly for cleaning up old snapshots. Snapshots older than 15 days will be deleted while a 5 minimum will always be kept. If a version is released, then all snapshots of this version will be removed.

If you want to selectively delete some snapshots, log into Nexus UI, go to the *Repositories* page and browse the *Snapshots* repository. In the repository tree view, right click on the node you want to delete and select *Delete*, just like this:

![2010-10-15-144404_741x521_scrot.png_version_1_modificationDate_1287125273453][]

#### 7a.3. Stage a Release ####

First you need to prepare a release:

$ mvn release:clean  
$ mvn release:prepare

Then stage the release:

$ mvn release:perform

Maven will checkout the tag you just prepared, then build and deploy it into Nexus staging repository.

### 7b. Stage Existing Artifacts ###

You don't have to go though the maven-release-plugin steps if your artifacts are already released. [maven-gpg-plugin][] can help sign and deploy artifacts.

For example, if you want to sign and deploy these artifacts:

ossrh-test-1.2.pom  
ossrh-test-1.2.jar  
ossrh-test-1.2-javadoc.jar  
ossrh-test-1.2-sources.jar

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(221,255,221); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/check.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Tip</strong><br> You can run&nbsp;<strong>mvn javadoc:jar</strong>&nbsp;and&nbsp;<strong>mvn source:jar</strong>&nbsp;respectively to generate -javadoc.jar and -sources.jar.<br> <em>by&nbsp;<a href="https://issues.sonatype.org/browse/OSSRH-1668" style="color:rgb(0,51,102)" rel="nofollow">Martijn Verburg</a></em></td> 
  </tr> 
 </tbody> 
</table>

Run commands like this:

$ mvn gpg:sign-and-deploy-file -Durl=[https://oss.sonatype.org/service/local/staging/deploy/maven2/][https_oss.sonatype.org_service_local_staging_deploy_maven2] -DrepositoryId=sonatype-nexus-staging -DpomFile=ossrh-test-1.2.pom -Dfile=ossrh-test-1.2.jar  
$ mvn gpg:sign-and-deploy-file -Durl=[https://oss.sonatype.org/service/local/staging/deploy/maven2/][https_oss.sonatype.org_service_local_staging_deploy_maven2] -DrepositoryId=sonatype-nexus-staging -DpomFile=ossrh-test-1.2.pom -Dfile=ossrh-test-1.2-sources.jar -Dclassifier=sources  
$ mvn gpg:sign-and-deploy-file -Durl=[https://oss.sonatype.org/service/local/staging/deploy/maven2/][https_oss.sonatype.org_service_local_staging_deploy_maven2] -DrepositoryId=sonatype-nexus-staging -DpomFile=ossrh-test-1.2.pom -Dfile=ossrh-test-1.2-javadoc.jar -Dclassifier=javadoc

Note that when you sign and deploy classifiers like sources and javadoc, you need to specify the *-Dclassifier* parameter.  
Besides, *-DrepositoryId* means you need to configure a matching server element in settings.xml like this:

<settings>
      ...
      <servers>
        ...
        <server>
          <id>sonatype-nexus-staging</id>
          <username>your-jira-id</username>
          <password>your-jira-pwd</password>
        </server>
      </servers>
      ...
    </settings>

The other way to stage existing artifacts is to create a bundle and upload it. For example, if you have the following artifacts:

ossrh-test-1.2.pom  
ossrh-test-1.2.pom.asc  
ossrh-test-1.2.jar  
ossrh-test-1.2.jar.asc  
ossrh-test-1.2-javadoc.jar  
ossrh-test-1.2-javadoc.jar.asc  
ossrh-test-1.2-sources.jar  
ossrh-test-1.2-sources.jar.asc

First create a bundle with a command like this:

$ jar -cvf bundle.jar ossrh-test-1.2.pom ossrh-test-1.2.pom.asc ossrh-test-1.2.jar ossrh-test-1.2.jar.asc ossrh-test-1.2-javadoc.jar ossrh-test-1.2-javadoc.jar.asc ossrh-test-1.2-sources.jar ossrh-test-1.2-sources.jar.asc

Then go to Nexus UI, click *Staging Upload* in the left column. In the Staging Upload panel, select *Artifact Bundle* as Upload Mode and select the bundle you just created, like this:

![2010-09-08-212630_724x246_scrot.png_version_1_modificationDate_1283952553323][]

Now click the *Upload Bundle* button, staging repository will be created and Nexus will run rules on it. You will get a report telling you if your artifacts are successfully staged and verified.

### 7c. Deploy Snapshots and Stage Releases with Ant ###

Maven repositories (even The Central Repository) are not limited to Maven users, Ant users can deploy artifacts to Maven repositories as well. First you need to manually create a *pom.xml*, which must contain all the elements specified in[Central Sync Requirements][].

Now your project directory should look like this:

build.xml  
pom.xml  
src/  
lib/  
...

Then install the Maven Ant Tasks. Download it from [http://maven.apache.org/ant-tasks/download.html][http_maven.apache.org_ant-tasks_download.html] and put it into *~/.ant/lib/*.

Now write your Ant build.xml like this:

Some explanation to the code above:

1.  **xmlns:artifact="antlib:org.apache.maven.artifact.ant"** is mandatory for installing Maven Ant Tasks
2.  you need to package a main jar artifact, a javadoc jar artifact and a sources jar artifact
3.  the **deploy** task uses Maven to deploy your main artifacts to the snapshot repository
4.  the **stage** task uses Maven to sign and deploy artifacts, you also need to [make sure GPG is correctly installed][How To Generate PGP Signatures With Maven]
5.  **maven-snapshots-repository-url** is the snapshot deploy URL, **maven-snapshots-repository-id** is used to identify it
6.  **maven-staging-repository-url** is the staging deploy URL, **maven-staging-repository-id** is used to identify it

To make the Ant script work, you also need to create a XML at *~/.m2/settings.xml*, with content like this:

<settings>
      <servers>
        <server>
          <id>sonatype-nexus-snapshots</id>
          <username>your-username</username>
          <password>your-password</password>
        </server>
        <server>
          <id>sonatype-nexus-staging</id>
          <username>your-username</username>
          <password>your-password</password>
        </server>
      </servers>
      <profiles>
        <profile>
          <id>gpg</id>
          <properties>
            <gpg.passphrase>xxxxxx</gpg.passphrase>
          </properties>
        </profile>
      </profiles>
    </settings>

1.  the <server> element is used to configure nexus access credential, its id must be identical to the value of **maven-snapshots-repository-id** and **maven-staging-repository-id** property in build.xml.
2.  the <profile> element is used to provide your gpg passphrase, it's not a good idea to put it directly into build.xml, so you should put passphrase here, and **<arg value="-Pgpg" />** in build.xml will make it work.

To deploy a SNAPSHOT, make sure the 'version' element in your *pom.xml* the 'version' property in your build.xml has a SNAPSHOT version value (like 1.0-SNAPSHOT), then run **ant deploy**.  
To stage a release, make sure the 'version' element in your *pom.xml* the 'version' property in your build.xml has a RELEASE version value (like 1.0), then run **ant stage**.

### 7d. Stage Releases with Gradle ###

Yennick Trevels wrote [an excellent article][] for Gradle users.

### 7e. Deploy and Stage with SBT ###

Here are some references to publishing to OSSRH with Scala Build Tool:

[http://www.cakesolutions.net/teamblogs/2012/01/28/publishing-sbt-projects-to-nexus/][http_www.cakesolutions.net_teamblogs_2012_01_28_publishing-sbt-projects-to-nexus]

[https://github.com/sbt/sbt.github.com/blob/gen-master/src/jekyll/using\_sonatype.md][https_github.com_sbt_sbt.github.com_blob_gen-master_src_jekyll_using_sonatype.md]

[https://raw.github.com/paulp/scala-improving/master/project/PublishToSonatype.scala][https_raw.github.com_paulp_scala-improving_master_project_PublishToSonatype.scala]

### 8a. Release It ###

To release your artifacts, open your favorite browser and go to Nexus UI with address: [https://oss.sonatype.org/][https_oss.sonatype.org].

To close a staging repository:

1.  Login to the Nexus UI.
2.  Go to Staging Repositories page.
3.  Select a staging repository.
4.  Click the Close button.

You will be asked to provide a description for this staging close operation. If the staging repository is closed successfully, you will get a notification email and confirmation via the ui.

See the image below for details.

![staging_close.png_version_1_modificationDate_1279720013166][]

To make sure the deployed artifacts meet the [Central Sync Requirements][] , Nexus has a few staging rules running on Staging Close and Release. These rules will validate your deployment has correct POM, javadoc, source, pgp signatures, and checksums etc. If your deployment has any problem, you will get a report like this:

![staging_rule_failure.png_version_1_modificationDate_1279720179943][]

Then you have to find out what's causing the problem, drop the staging repository, fix your release, and deploy again.

After staging repository is closed successfully, you can click on it to get a repository tree view. You will want to download them and do some manual testing  (or hold a community vote) before finally releasing them. To download an artifact, right click on it and select Download.

![staging_closed.png_version_1_modificationDate_1280153165778][]

In these 2 cases you will want to drop a staging/staged repository:

1.  Staging rules fail to pass when you try to close a staging repository, so you have to drop it.
2.  Staging repository is closed, but when you test the artifacts in the staged repository, you find some problems. So you will want to drop it and stage again.

To drop a staging repository, select it and click the Drop button, see the image below.

![staging_drop.png_version_1_modificationDate_1279720325059][]

When you are sure the closed staging repository has no problem, click the Release button. You will be asked to input a description for this release. Staging rules will run again. If the closed staging repository is released successfully, you will get a notification email. Now your artifacts are in the **Releases** repository, which is synced to The Central Repository roughly every 2 hours. Now you can browse or search your artifacts from Nexus UI.

![staging_release.png_version_1_modificationDate_1279720544670][]

### 8b. Automating Releases ###

You are not limited to using the Nexus Web UI to close/release your Staging repositories. If you want to automate the Staging process, you can use the Nexus Staging Maven Plugin or Ant Tasks. Please read [Build Promotion with the Nexus Staging Suite][] in the book *Repository Management with Nexus* for more information.

### 8c. Automating Releases in Nexus 2.4 ###

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; background-color:rgb(255,255,206); padding:0px 20px; width:1325px">     
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"> <img src="https://docs.sonatype.org/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt=""></td> 
   <td style="font-size:1em; line-height:13pt; padding:14px 0px; border:none"><strong>Note</strong><br> Please consult&nbsp;<strong><a href="http://books.sonatype.com/nexus-book/reference/staging-sect-deployment.html#staging-sect-deployment-nexus-staging-maven-plugin" style="color:rgb(0,51,102)" rel="nofollow">this section</a></strong>&nbsp;of&nbsp;<em>Repository Management with Nexus</em>&nbsp;for instructions on using the nexus-staging-maven-plugin with Nexus 2.4.<br> The links below will take you to detailed documentation on the plugins themselves.</td> 
  </tr> 
 </tbody> 
</table>

Once OSSRH is upgraded to version 2.4 of Nexus, users who have been automating the close and/or release of staging repositories may need to modify their build procedures in the following scenarios:

*  Users who use the [nexus-maven-plugin][] will have to use [nexus-staging-maven-plugin][] version 1.4.4
 *  Users who already use the [nexus-staging-maven-plugin][] will have to upgrade to version 1.4.4. This should be as simple as changing the version element for the plugin in your POM.
 *  Users who use [nexus-ant tasks][] will have to upgrade to version 1.4
 *  Users who are calling the REST API directly to close/release staging repositories you will need to consult the Nexus 2.4 API documentation to determine what changes they may need to make. The new API calls will be available here after the upgrade is complete: [https://oss.sonatype.org/nexus-staging-plugin/default/docs/index.html][https_oss.sonatype.org_nexus-staging-plugin_default_docs_index.html]

### 9. Activate Central Sync ###

The first time you promote a release, **you need to** comment on the OSSRH JIRA ticket you created in *Section 3* so we can know you are ready to be synced. We will review your promoted artifacts. If no problem found, we will activate Central Sync for you and close your JIRA ticket.

After Central Sync is activated, your future promotion will be synced automatically. The sync process runs roughly every 2 hours.

### 10. Help ###

We have created two mailing lists for OSSRH Users:

<table style="font-size:10pt; line-height:13pt; color:rgb(0,0,0); clear:left; margin:5px 0px; border-collapse:collapse; padding:0px"> 
 <tbody> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <th style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; background-color:rgb(240,240,240); vertical-align:top; min-width:0.6em; color:rgb(0,51,102)"> List Address&nbsp;<br> </th> 
   <th style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; background-color:rgb(240,240,240); vertical-align:top; min-width:0.6em; color:rgb(0,51,102)"> Unsubscribe&nbsp;<br> </th> 
   <th style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; background-color:rgb(240,240,240); vertical-align:top; min-width:0.6em; color:rgb(0,51,102)"> Subscribe&nbsp;<br> </th> 
  </tr> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> ossrh-announcements@sonatype.org</td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> ossrh-announcements-unsubscribe@sonatype.org</td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> ossrh-announcements-subscribe@sonatype.org</td> 
  </tr> 
  <tr style="font-size:10pt; line-height:13pt"> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> ossrh-users@sonatype.org&nbsp;<br> </td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> ossrh-users-unsubscribe@sonatype.org</td> 
   <td style="font-size:10pt; line-height:13pt; border:1px solid rgb(221,221,221); padding:5px; vertical-align:top; min-width:0.6em"> ossrh-users-subscribe@sonatype.org</td> 
  </tr> 
 </tbody> 
</table>

Upon account creation, you will automatically be added to the Announcements List. This list will be used for outbound announcements regarding system upgrades and other changes that affect your projects. All replies to this list are redirected back to the user list which is where more general discussion in the community will take place.

You can also come to our IRC (irc.codehaus.org, channel \#mavencentral).

### 11. What Do People Think About OSSRH ###

*  [Automated Gradle project deployment to Sonatype OSS Repository][an excellent article] by *Yennick Trevels* on *Nov 5, 2011*
 *  [Want to host on Maven Central?][Want to host on Maven Central] by *Kvahuja* on *Sep 8, 2011*
 *  [Deployer un artefact sur repo1.maven.org \[French\]][Deployer un artefact sur repo1.maven.org _French] by *Issam El Fatmi* and *Cyrille Le Clerc* on *Jul 22, 2011*
 *  [How to upload your artifacts to maven central][] by *umut.utkan* on *Apr 24, 2011*
 *  [Releasing Maven Artifacts to Central Repository through Sonatype][] by *Jarrod Roberson* on *Mar 22, 2011*
 *  [Automating publishing to maven central via Sonatype][] by *Yan Pujante* on *Nov 27, 2010*
 *  [Publishing javassist releases to Sonatype public repo/maven central][Publishing javassist releases to Sonatype public repo_maven central] by *Andrew Dinn* on *Jul 27, 2010*
 *  [Automating Releases with maven-release-plugin \[covered a lot on CVS and PGP\]][Automating Releases with maven-release-plugin _covered a lot on CVS and PGP] by *Michael Remijan* on *May 20, 2010*
 *  [Free Maven Repository Hosting for Open Source projects by Sonatype][] by *James Lorenzen* on *Mar 1, 2010*
 *  [Sonatype Free Maven Repository Hosting For FLOSS projects - Great Stuff!][Sonatype Free Maven Repository Hosting For FLOSS projects - Great Stuff] by *Fabrizio Giudici* on *Feb 26, 2010*
 *  [Releasing a project to Maven Central repository via Sonatype][] by *Jakub Holý* on *Feb 7, 2010*

[https_docs.sonatype.org_display_Repository_Sonatype_OSS_Maven_Repository_Usage_Guide]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
[Attachments_4]: https://docs.sonatype.org/pages/viewpageattachments.action?pageId=6619209&metadataLink=true
[Juven Xu]: https://docs.sonatype.org/display/~juven
[Joel Orlina]: https://docs.sonatype.org/display/~jorlina
[view change]: https://docs.sonatype.org/pages/diffpages.action?pageId=6619209&originalId=12550216
[1. Introduction]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-1.Introduction
[1a. Terms of Service]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-1a.TermsofServiceRepository%3ACentralRepositoryTermsofServiceforSubmitters
[2. Sign up]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-2.Signup
[3. Create a JIRA ticket]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-3.CreateaJIRAticket
[4. Maven Repositories]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-4.MavenRepositories
[5. Prerequisites]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-5.Prerequisites
[6. Central Sync Requirement]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-6.CentralSyncRequirement
[7a. Deploy Snapshots and Stage Releases with Maven]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7a.DeploySnapshotsandStageReleaseswithMaven
[7a.1. POM and settings config]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7a.1.POMandsettingsconfig
[7a.2. Publish Snapshots]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7a.2.PublishSnapshots
[7a.3. Stage a Release]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7a.3.StageaRelease
[7b. Stage Existing Artifacts]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7b.StageExistingArtifacts
[7c. Deploy Snapshots and Stage Releases with Ant]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7c.DeploySnapshotsandStageReleaseswithAnt
[7d. Stage Releases with Gradle]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7d.StageReleaseswithGradle
[7e. Deploy and Stage with SBT]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-7e.DeployandStagewithSBT
[8a. Release It]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-8a.ReleaseIt
[8b. Automating Releases]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-8b.AutomatingReleases
[8c. Automating Releases in Nexus 2.4]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-8c.AutomatingReleasesinNexus2.4
[9. Activate Central Sync]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-9.ActivateCentralSync
[10. Help]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-10.Help
[11. What Do People Think About OSSRH]: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-11.WhatDoPeopleThinkAboutOSSRH
[Nexus]: http://nexus.sonatype.org/
[https_oss.sonatype.org]: https://oss.sonatype.org/
[The Central Repository]: http://repo1.maven.org/maven2/
[1a. Terms of Service 1]: https://docs.sonatype.org/display/Repository/Central+Repository+Terms+of+Service+for+Submitters
[https_issues.sonatype.org]: https://issues.sonatype.org/
[sign_up_1.png_version_1_modificationDate_1276583992178]: https://docs.sonatype.org/download/attachments/6619209/sign_up_1.png?version=1&modificationDate=1276583992178
[sign_up_2.png_version_1_modificationDate_1276584039405]: https://docs.sonatype.org/download/attachments/6619209/sign_up_2.png?version=1&modificationDate=1276584039405
[Sonatype Open Source Project Repository Hosting JIRA]: https://issues.sonatype.org/browse/OSSRH
[http_subversion.apache.org]: http://subversion.apache.org/
[http_www.gnupg.org]: http://www.gnupg.org/
[How To Generate PGP Signatures With Maven]: https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
[Improve The Central Repository and the Supporting the Maven Ecosystem]: http://www.sonatype.com/people/2010/01/nexus-oss-ecosystem/
[3rd-party artifacts bundle upload service]: https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
[Why Putting Repositories in your POMs is a Bad Idea]: http://www.sonatype.com/people/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/
[Why external repos are being phased out of Central]: http://www.sonatype.com/people/2010/03/why-external-repos-are-being-phased-out-of-central/
[Sonatype OSS Parent POM]: http://repo1.maven.org/maven2/org/sonatype/oss/oss-parent/7/oss-parent-7.pom
[2010-10-15-144404_741x521_scrot.png_version_1_modificationDate_1287125273453]: https://docs.sonatype.org/download/attachments/6619266/2010-10-15-144404_741x521_scrot.png?version=1&modificationDate=1287125273453
[maven-gpg-plugin]: http://maven.apache.org/plugins/maven-gpg-plugin/
[https_oss.sonatype.org_service_local_staging_deploy_maven2]: https://oss.sonatype.org/service/local/staging/deploy/maven2/
[2010-09-08-212630_724x246_scrot.png_version_1_modificationDate_1283952553323]: https://docs.sonatype.org/download/attachments/7045234/2010-09-08-212630_724x246_scrot.png?version=1&modificationDate=1283952553323
[Central Sync Requirements]: https://docs.sonatype.org/display/Repository/Central+Sync+Requirements
[http_maven.apache.org_ant-tasks_download.html]: http://maven.apache.org/ant-tasks/download.html
[an excellent article]: http://jedicoder.blogspot.com/2011/11/automated-gradle-project-deployment-to.html
[http_www.cakesolutions.net_teamblogs_2012_01_28_publishing-sbt-projects-to-nexus]: http://www.cakesolutions.net/teamblogs/2012/01/28/publishing-sbt-projects-to-nexus/
[https_github.com_sbt_sbt.github.com_blob_gen-master_src_jekyll_using_sonatype.md]: https://github.com/sbt/sbt.github.com/blob/gen-master/src/jekyll/using_sonatype.md
[https_raw.github.com_paulp_scala-improving_master_project_PublishToSonatype.scala]: https://raw.github.com/paulp/scala-improving/master/project/PublishToSonatype.scala
[staging_close.png_version_1_modificationDate_1279720013166]: https://docs.sonatype.org/download/attachments/6619276/staging_close.png?version=1&modificationDate=1279720013166
[staging_rule_failure.png_version_1_modificationDate_1279720179943]: https://docs.sonatype.org/download/attachments/6619276/staging_rule_failure.png?version=1&modificationDate=1279720179943
[staging_closed.png_version_1_modificationDate_1280153165778]: https://docs.sonatype.org/download/attachments/6619276/staging_closed.png?version=1&modificationDate=1280153165778
[staging_drop.png_version_1_modificationDate_1279720325059]: https://docs.sonatype.org/download/attachments/6619280/staging_drop.png?version=1&modificationDate=1279720325059
[staging_release.png_version_1_modificationDate_1279720544670]: https://docs.sonatype.org/download/attachments/6619284/staging_release.png?version=1&modificationDate=1279720544670
[Build Promotion with the Nexus Staging Suite]: http://www.sonatype.com/books/nexus-book/reference/staging.html
[nexus-maven-plugin]: https://repository.sonatype.org/content/sites/maven-sites/nexus-maven-plugin/
[nexus-staging-maven-plugin]: https://github.com/sonatype/nexus-maven-plugins/tree/master/staging/maven-plugin
[nexus-ant tasks]: https://github.com/sonatype/nexus-ant-tasks/tree/master/nexus-staging-ant-tasks
[https_oss.sonatype.org_nexus-staging-plugin_default_docs_index.html]: https://oss.sonatype.org/nexus-staging-plugin/default/docs/index.html
[Want to host on Maven Central]: http://scratchpad101.com/2011/09/08/project-files-maven-central/
[Deployer un artefact sur repo1.maven.org _French]: http://blog.xebia.fr/2011/06/22/deployer-un-artefact-sur-repo1-maven-org/
[How to upload your artifacts to maven central]: http://www.codinginahurry.com/2011/04/24/how-to-upload-your-artifacts-to-maven-central/
[Releasing Maven Artifacts to Central Repository through Sonatype]: http://www.vertigrated.com/blog/2011/03/releasing-maven-artifacts-to-central-repository-through-sonatype/
[Automating publishing to maven central via Sonatype]: http://www.pongasoft.com/blog/yan/entry/automating_publishing_to_maven_central/
[Publishing javassist releases to Sonatype public repo_maven central]: http://community.jboss.org/wiki/PublishingJavassistReleasesToSonatypePublicRepomavenCentral
[Automating Releases with maven-release-plugin _covered a lot on CVS and PGP]: http://java.dzone.com/articles/automating-releases-maven-0
[Free Maven Repository Hosting for Open Source projects by Sonatype]: http://jlorenzen.blogspot.com/2010/03/free-maven-repository-hosting-for-open.html
[Sonatype Free Maven Repository Hosting For FLOSS projects - Great Stuff]: http://java.dzone.com/news/sonatype-free-maven-repo
[Releasing a project to Maven Central repository via Sonatype]: http://theholyjava.wordpress.com/2010/02/07/releasing-a-project-to-maven-centr/