jspwiki-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r890975 - in /websites/staging/jspwiki/trunk/content: ./ ppmc/how_to_release.html
Date Wed, 18 Dec 2013 23:53:00 GMT
Author: buildbot
Date: Wed Dec 18 23:53:00 2013
New Revision: 890975

Log:
Staging update by buildbot for jspwiki

Modified:
    websites/staging/jspwiki/trunk/content/   (props changed)
    websites/staging/jspwiki/trunk/content/ppmc/how_to_release.html

Propchange: websites/staging/jspwiki/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Dec 18 23:53:00 2013
@@ -1 +1 @@
-1552166
+1552167

Modified: websites/staging/jspwiki/trunk/content/ppmc/how_to_release.html
==============================================================================
--- websites/staging/jspwiki/trunk/content/ppmc/how_to_release.html (original)
+++ websites/staging/jspwiki/trunk/content/ppmc/how_to_release.html Wed Dec 18 23:53:00 2013
@@ -310,31 +310,37 @@ changes on the front page of the site</p
 
 <h2 id="add-the-next-release-to-jira">Add the next release to JIRA</h2>
 <ol>
-<li>Add the <a href="https://issues.apache.org/jira/plugins/servlet/project-config/jspwiki/versions">next
version number to JIRA</a></li>
-<li>Mark the released version as "released" with a release date</li>
+<li>
+<p>Add the <a href="https://issues.apache.org/jira/plugins/servlet/project-config/jspwiki/versions">next
version number to JIRA</a></p>
+</li>
+<li>
+<p>Mark the released version as "released" with a release date</p>
+</li>
 </ol>
 <h2 id="troubleshooting">Troubleshooting</h2>
 <ol>
-<li>Cygwin mixes Windows path with cygdrive, so <code>mvn release:prepare</code>
fails on svn commit</li>
-</ol>
+<li>
+<p>Cygwin mixes Windows path with cygdrive, so <code>mvn release:prepare</code>
fails on svn commit</p>
 <p>Current workaround: perform release vía <code>cmd.exe</code></p>
-<ol>
-<li>Avoid gpg signing prompt when using Maven release plugin</li>
-</ol>
+</li>
+<li>
+<p>Avoid gpg signing prompt when using Maven release plugin</p>
 <p>See <a href="http://stackoverflow.com/q/14114528">http://stackoverflow.com/q/14114528</a></p>
-<ol>
-<li><code>mvn release:prepare</code> doesn't find svn credentials</li>
-</ol>
+</li>
+<li>
+<p><code>mvn release:prepare</code> doesn't find svn credentials</p>
 <p>On your settings.xml file you should have one <server /> entry for each of
the following ones:
 <em> <code>apache.snapshots.https</code>: to be able to deploy snapshots
 </em> <code>apache.releases.https</code>: to be able to deploy releases
-* <code>svn.apache.org</code>: to be able to create tags
-Alternatively, for the last one, you could pass -Dusername=[username] -Dpassword=[password]
to the mvn command 
+* <code>svn.apache.org</code>: to be able to create tags</p>
+<p>Alternatively, for the last one, you could pass -Dusername=[username] -Dpassword=[password]
to the mvn command 
 (source: <a href="http://stackoverflow.com/q/1255593">http://stackoverflow.com/q/1255593</a>)</p>
-<ol>
-<li>Release fails after a tag has been generated and the pom versions have been incremented</li>
-</ol>
+</li>
+<li>
+<p>Release fails after a tag has been generated and the pom versions have been incremented</p>
 <p>No need of <code>mvn release:rollback</code>, instead check out the
tag and <code>release:perform -DconnectionUrl=scm:svn:https://svn.apache.org/COMPLETE-URL-TO-TAG</code></p>
+</li>
+</ol>
 <h2 id="other-links-of-interest">Other links of interest</h2>
 <ul>
 <li><a href="https://confluence.sakaiproject.org/display/REL/Maven+release+plugin+cheat+sheet">Maven
release plugin cheat sheet</a></li>



Mime
View raw message