You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by se...@apache.org on 2013/06/08 01:03:11 UTC

svn commit: r1490862 - /commons/cms-site/trunk/content/xdoc/releases/prepare.xml

Author: sebb
Date: Fri Jun  7 23:03:11 2013
New Revision: 1490862

URL: http://svn.apache.org/r1490862
Log:
Reminder re using java profile

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=1490862&r1=1490861&r2=1490862&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Fri Jun  7 23:03:11 2013
@@ -517,11 +517,11 @@
 
     <p>To create all distributables and upload the Maven artifacts to the ASF Nexus instance run
       <pre>
-        mvn deploy -Prelease
+        mvn deploy -Prelease [-Pjava-1.x]
       </pre>
       If you want to do a test deployment first, you can add the following option:
       <pre>
-        mvn deploy -Prelease -Ptest-deploy
+        mvn deploy -Prelease -Ptest-deploy [-Pjava-1.x]
       </pre>
       The "test-deploy" profile uploads the artifacts to target/deploy instead of Nexus so one can check all the required files
       have been created with the expected contents.