You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shindig.apache.org by rb...@apache.org on 2013/10/05 23:45:49 UTC
svn commit: r1529528 - /shindig/site/trunk/cms/trunk/content/releasing.mdtext
Author: rbaxter85
Date: Sat Oct 5 21:45:49 2013
New Revision: 1529528
URL: http://svn.apache.org/r1529528
Log:
Adding additional info
Modified:
shindig/site/trunk/cms/trunk/content/releasing.mdtext
Modified: shindig/site/trunk/cms/trunk/content/releasing.mdtext
URL: http://svn.apache.org/viewvc/shindig/site/trunk/cms/trunk/content/releasing.mdtext?rev=1529528&r1=1529527&r2=1529528&view=diff
==============================================================================
--- shindig/site/trunk/cms/trunk/content/releasing.mdtext (original)
+++ shindig/site/trunk/cms/trunk/content/releasing.mdtext Sat Oct 5 21:45:49 2013
@@ -76,6 +76,10 @@ by default in the build (for productivit
2. Preparing the release will create a new tag in SVN, automatically checking in on your
behalf. Verify the SVN logs in the [Commit List](mail-lists.html) or review the generated tag.
3. All license headers and legal files will be checked by RAT (Release Audit Tool).
+4. Instead of configuring your Maven environment to store your SVN credentials you can pass them on the command line, for example
+<pre>
+mvn release:prepare -Papache-release -Dusername=username -Dpassword=password
+</pre>
## 3. Stage The Release