You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by bu...@apache.org on 2013/06/08 01:03:31 UTC
svn commit: r864773 - in /websites/staging/commons/trunk/content: ./
releases/prepare.html
Author: buildbot
Date: Fri Jun 7 23:03:31 2013
New Revision: 864773
Log:
Staging update by buildbot for commons
Modified:
websites/staging/commons/trunk/content/ (props changed)
websites/staging/commons/trunk/content/releases/prepare.html
Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jun 7 23:03:31 2013
@@ -1 +1 @@
-1490858
+1490862
Modified: websites/staging/commons/trunk/content/releases/prepare.html
==============================================================================
--- websites/staging/commons/trunk/content/releases/prepare.html (original)
+++ websites/staging/commons/trunk/content/releases/prepare.html Fri Jun 7 23:03:31 2013
@@ -659,11 +659,11 @@
<p>To create all distributables and upload the Maven artifacts to the ASF Nexus instance run
</p><div><pre>
- mvn deploy -Prelease
+ mvn deploy -Prelease [-Pjava-1.x]
</pre></div>
If you want to do a test deployment first, you can add the following option:
<div><pre>
- mvn deploy -Prelease -Ptest-deploy
+ mvn deploy -Prelease -Ptest-deploy [-Pjava-1.x]
</pre></div>
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.