aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From z..@apache.org
Subject svn commit: r783719 - in /websites/production/aries: ./ content/development/releasingaries.html
Date Fri, 21 Jan 2011 17:27:31 GMT
Author: zoe
Date: Fri Jan 21 17:27:31 2011
New Revision: 783719

Log:
fix a couple of typos

Modified:
    websites/production/aries/   (props changed)
    websites/production/aries/content/development/releasingaries.html

Propchange: websites/production/aries/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Fri Jan 21 17:27:31 2011
@@ -1 +1 @@
-/websites/staging/aries/trunk:782169-783642
+/websites/staging/aries/trunk:782169-783718

Modified: websites/production/aries/content/development/releasingaries.html
==============================================================================
--- websites/production/aries/content/development/releasingaries.html (original)
+++ websites/production/aries/content/development/releasingaries.html Fri Jan 21 17:27:31
2011
@@ -348,7 +348,7 @@ failures, the easiest way I've found so 
 
 <p>This will pick out the failing file names. Some of the files that rat fails
 do not require an Apache license, eg MANIFEST.MF, but any <em>.java or </em>.js
-file does need one.</p>
+file does need one. As an alternative you can use 'mvn -Prat install'.</p>
 <p><a name="ReleasingAries-Creatingasnapshotrelease"></a></p>
 <h3 id="creating_a_snapshot_release">Creating a snapshot release</h3>
 <p>TBD. This isn't a necessary step in the release process but should still be
@@ -379,7 +379,7 @@ because everything else depends on it. R
 
 
 <p><em>Note</em> The prepare step will make some assumptions about the
version of the
-development steam that is left after the release has been made. When
+development stream that is left after the release has been made. When
 releasing from a branch it may not be a good idea to accept the default for
 this, it will very likely conflict with the development version in use in
 trunk.</p>
@@ -422,17 +422,21 @@ it to restart where it left off.</p>
 
 
 <p>Then for each project, in the order given below:</p>
-<p>testsupport
-util
-blueprint 
-jndi
-transaction
-web
-application
-jmx
-quiesce
-jpa
-samples <em>See Note 1 below</em></p>
+<div class="codehilite"><pre><span class="n">testsupport</span>
+<span class="n">util</span>
+<span class="n">proxy</span>
+<span class="n">blueprint</span> 
+<span class="n">jndi</span>
+<span class="n">transaction</span>
+<span class="n">web</span>
+<span class="n">application</span>
+<span class="n">jmx</span>
+<span class="n">quiesce</span>
+<span class="n">jpa</span>
+<span class="n">samples</span> <span class="o">*</span><span class="n">See</span>
<span class="n">Note</span> <span class="mi">1</span> <span class="n">below</span><span
class="o">*</span>
+</pre></div>
+
+
 <p>Run the following commands:</p>
 <div class="codehilite"><pre><span class="n">mvn</span> <span
class="n">versions:update</span><span class="o">-</span><span class="n">parent</span>
 <span class="n">mvn</span> <span class="n">versions:use</span><span
class="o">-</span><span class="n">releases</span>



Mime
View raw message