commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bode...@apache.org
Subject svn commit: r1457209 - /commons/cms-site/trunk/content/xdoc/releases/prepare.xml
Date Sat, 16 Mar 2013 06:28:44 GMT
Author: bodewig
Date: Sat Mar 16 06:28:44 2013
New Revision: 1457209

URL: http://svn.apache.org/r1457209
Log:
Initial Nexus hints

Modified:
    commons/cms-site/trunk/content/xdoc/releases/prepare.xml

Modified: commons/cms-site/trunk/content/xdoc/releases/prepare.xml
URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/prepare.xml?rev=1457209&r1=1457208&r2=1457209&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Sat Mar 16 06:28:44 2013
@@ -31,6 +31,13 @@
 	The instructions provided here are consistent with, but not a replacement for
 	the <a href="http://www.apache.org/dev/release.html">ASF Release Guidlines.</a>

 	</p>
+    <p>Commons uses the Nexus installation at the Apache Software Foundation to stage
Maven artifacts
+    before the release and later publish them, the Commons Parent POM contains all the necessary
configuration.
+    This guide covers deploying to Nexus using Maven, for alternatives see
+    <a href="http://www.apache.org/dev/publishing-maven-artifacts.html">the ASF wide
documentation</a>.
+    If this is the first time you are publishing to the ASF's Nexus instance
+    you'll need to <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env">prepare
+    your development environment</a>.</p>
     <p>
     The examples below assume that preparation is being made to release version <em>1.2</em>
     of component <em>Foo</em>.
@@ -41,7 +48,7 @@
     Commons components are expected to use Maven to build the project website. Components
     may choose to use either Maven or Ant to build the actual jar and tar/zip files to be
distributed,
     although it is recommended that Maven be used for this. Both approaches are covered
-    below.  The version of Maven used is assumed to be Maven 2 throughout.  At a minimum,
Commons
+    below.  The version of Maven used is assumed to be Maven 3 throughout.  At a minimum,
Commons
     releases <strong>must</strong> include full source distributions packaged
in tar and zip
     archives.
     </p>
@@ -170,7 +177,9 @@
       &lt;properties&gt;
         &lt;commons.componentid&gt;foo&lt;/commons.componentid&gt;
         &lt;commons.release.version&gt;1.2&lt;/commons.release.version&gt;
-        &lt;commons.binary.suffix&gt;&lt;/commons.binary.suffix&gt;
+        &lt;commons.rc.version&gt;RC1&lt;/commons.rc.version&gt;
+
+        &lt;-- properties not related to versioning --&gt;
         &lt;commons.jira.id&gt;FOO&lt;/commons.jira.id&gt;
         &lt;commons.jira.pid&gt;007&lt;/commons.jira.pid&gt;
         &lt;maven.compile.source&gt;1.3&lt;/maven.compile.source&gt;



Mime
View raw message