aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From z..@apache.org
Subject svn commit: r1062445 - /aries/site/trunk/content/development/releasingaries.mdtext
Date Sun, 23 Jan 2011 15:03:28 GMT
Author: zoe
Date: Sun Jan 23 15:03:28 2011
New Revision: 1062445

URL: http://svn.apache.org/viewvc?rev=1062445&view=rev
Log:
Add a comment

Modified:
    aries/site/trunk/content/development/releasingaries.mdtext

Modified: aries/site/trunk/content/development/releasingaries.mdtext
URL: http://svn.apache.org/viewvc/aries/site/trunk/content/development/releasingaries.mdtext?rev=1062445&r1=1062444&r2=1062445&view=diff
==============================================================================
--- aries/site/trunk/content/development/releasingaries.mdtext (original)
+++ aries/site/trunk/content/development/releasingaries.mdtext Sun Jan 23 15:03:28 2011
@@ -240,7 +240,7 @@ Then for each project, in the order give
 Run the following commands:
 
     mvn versions:update-parent
-    mvn versions:use-releases
+    mvn versions:use-releases *See Note 3 below*
     svn commit -m "updated to latest releases"
     rm pom.xml.versionsBackup
     mvn release:prepare -Papache-release -DpreparationGoals="clean install"
@@ -255,6 +255,9 @@ the version element for the module itsel
   * Note 2: -DpreparationGoals="clean install"	is needed for all modules
 that have sub modules with dependencies between them, in practice this is
 most modules.
+  * Note 3: These two commands should only make changes to the top level pom.xml. However,
this relies on people having 
+understood that all the modules' dependencies go in the top level pom. If they haven't it's
better 
+to fix the poms before releasing.
 
 
 <a name="ReleasingAries-Closingthestagingrepository"></a>



Mime
View raw message