Author: britter
Date: Sun Oct 15 09:57:02 2017
New Revision: 1812215
URL: http://svn.apache.org/viewvc?rev=1812215&view=rev
Log:
Always run clean before deploying to the staging repository
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=1812215&r1=1812214&r2=1812215&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Sun Oct 15
09:57:02 2017
@@ -635,11 +635,11 @@ mvn versions:display-plugin-updates -U</
<p>To create all distributables and upload the Maven artifacts to the <a
href="http://repository.apache.org">ASF Nexus instance</a> run
<pre>
- mvn deploy -Prelease -Duser.name=<your apache ID> [-Pjava-1.x]
+ mvn clean deploy -Prelease -Duser.name=<your apache ID>
[-Pjava-1.x]
</pre>
If you want to do a test deployment first, you can add the following
options:
<pre>
- mvn deploy -Prelease -Duser.name=<your apache ID> -Ptest-deploy
[-Pjava-1.x] [-Dgpg.skip]
+ mvn clean deploy -Prelease -Duser.name=<your apache ID>
-Ptest-deploy [-Pjava-1.x] [-Dgpg.skip]
</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.