Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Commons Wiki" for 
change notification.

The "UsingNexus" page has been changed by sebbapache.
http://wiki.apache.org/commons/UsingNexus?action=diff&rev1=6&rev2=7

--------------------------------------------------

  If the vote succeeds, the artifacts can be promoted to the live repository.
  If it fails, the artifacts can be deleted, and the process can restart.
  
+ It also allows redundant files (such as .asc.md5 and .asc.sha1 hashes) to be 
deleted before deployment.
+ 
  == Preparations for using Nexus ==
  
-  * All Commons projects that use the org.apache.commons groupId are already 
set up to use Nexus. However, ones that use different groupIds may need to be 
set up.
+  * All Commons components that use the ''org.apache.commons'' groupId are 
already set up to use Nexus. 
+ However, components that use different groupIds may need to be set up.
  Just create a JIRA subtask under 
https://issues.apache.org/jira/browse/INFRA-1896, for example see: 
https://issues.apache.org/jira/browse/INFRA-2725 (Commons) or 
https://issues.apache.org/jira/browse/INFRA-2799 (CLI)
  
   * If you have not done so already, create a master password.
@@ -60, +63 @@

  == How to use deploy using Nexus ==
  
  As noted above, there are two different repositories, one for snapshots and 
the other for releases.
- If the version contains the suffix -SNAPSHOT, then the snapshot repo will be 
chosen by '''mvn deploy''' otherwise it will use the release repo.
+ If the version contains the suffix '''-SNAPSHOT''', then the snapshot repo 
will be chosen by '''mvn deploy''' otherwise deploy will use the release repo.
  
  === Creating a Nexus snapshot ===
  
  In the run-up to a release, it is worth-while creating a snapshot.
  This will allow checking of the artifacts, as well as checking that the 
settings are correct.
  
- To create the snapshot, make sure that the current directory is for a 
SNAPSHOT version. Perform the following command:
+ To create the snapshot, make sure that the current pom.xml is for a SNAPSHOT 
version. Perform the following command:
  
  {{{mvn deploy -Prelease [-Dgpg.skip] [-DskipTests]}}}
  
@@ -101, +104 @@

  }}}
  
  You can then add {{{-Plocal-deploy}}} to the deploy command to change the 
deployment to use {{{target/deploy}}}.
+ 
  === Creating a Nexus staging release ===
  
- '''THIS SECTION IS INCOMPLETE - DO NOT USE YET'''
+ '''Make sure you are using Commons Parent V16 or later.'''
  
- Make sure you are using Commons Parent V16 or later.
  This is necessary to ensure that Nexus is used as the deployment target.
  
  First, create the SVN tag (with appropriate non-SNAPSHOT version in the pom), 
check it out into a fresh workspace and build/test the code.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to