ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From maart...@apache.org
Subject svn commit: r1311139 - in /ant/ivy/core/branches/2.3.x: ./ doc/dev/makerelease.html doc/dev/updatesite.html doc/toc.json
Date Mon, 09 Apr 2012 06:34:01 GMT
Author: maartenc
Date: Mon Apr  9 06:34:00 2012
New Revision: 1311139

URL: http://svn.apache.org/viewvc?rev=1311139&view=rev
Log:
Merged documentation changes from trunk.

Removed:
    ant/ivy/core/branches/2.3.x/doc/dev/updatesite.html
Modified:
    ant/ivy/core/branches/2.3.x/   (props changed)
    ant/ivy/core/branches/2.3.x/doc/dev/makerelease.html
    ant/ivy/core/branches/2.3.x/doc/toc.json

Propchange: ant/ivy/core/branches/2.3.x/
------------------------------------------------------------------------------
  Merged /ant/ivy/core/trunk:r1310241-1310243

Modified: ant/ivy/core/branches/2.3.x/doc/dev/makerelease.html
URL: http://svn.apache.org/viewvc/ant/ivy/core/branches/2.3.x/doc/dev/makerelease.html?rev=1311139&r1=1311138&r2=1311139&view=diff
==============================================================================
--- ant/ivy/core/branches/2.3.x/doc/dev/makerelease.html (original)
+++ ant/ivy/core/branches/2.3.x/doc/dev/makerelease.html Mon Apr  9 06:34:00 2012
@@ -111,7 +111,7 @@ You can for example add a HEADER.html li
 
 <h3>11. Prepare the Eclipse update site</h3>
 
-To be able to test the release within IvyDE, it can be deployed in the IvyDE update site.
See <a href="updatesite.html">that page</a> to know how to process.
+To be able to test the release within IvyDE, it can be deployed in the IvyDE update site.
See <a href="http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html">that
page</a> to know how to process.
 
 <h3>12. Tag the svn repository</h3>
 As soon as you are happy with the artifacts to be released, it is time to tag the svn repo
@@ -161,8 +161,7 @@ If the release is approved, it's now tim
 
 If the release candidate has been staged into the dev area, then just do:
 <code>
-$ svn copy https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION https://dist.apache.org/repos/dist/release/ant/ivy/$VERSION
-$ svn rm https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION
+$ svn mv https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION https://dist.apache.org/repos/dist/release/ant/ivy/$VERSION
 </code>
 
 If the candidate has been published on people.apache.org, just directly commit the artifacts
into the subversion repository https://dist.apache.org/repos/dist/release/ant/ 
@@ -218,7 +217,7 @@ ant /all generate-site-ivy
 
 <h3>16. Deploy the Eclipse updatesite</h3>
 
-If the Eclipse update site has already been prepared to include that new Ivy release, it
is now needed to be deployed. Then follow the deployment instruction on <a href="updatesite.html">that
page</a>.
+If the Eclipse update site has already been prepared to include that new Ivy release, it
is now needed to be deployed. Then follow the deployment instruction on <a href="http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html">that
page</a>.
 
 <h3>17. Announce</h3>
 Announce the release on the dev@ant.a.o, ivy-user@ant.a.o, user@ant.apache.org and announce@apache.org
mailing lists.

Modified: ant/ivy/core/branches/2.3.x/doc/toc.json
URL: http://svn.apache.org/viewvc/ant/ivy/core/branches/2.3.x/doc/toc.json?rev=1311139&r1=1311138&r2=1311139&view=diff
==============================================================================
--- ant/ivy/core/branches/2.3.x/doc/toc.json (original)
+++ ant/ivy/core/branches/2.3.x/doc/toc.json Mon Apr  9 06:34:00 2012
@@ -902,13 +902,6 @@
                     "children": [
 
                       ]
-                  },
-                  {
-                    "id":"dev/updatesite",
-                    "title":"Updating the updatesite",
-                    "children": [
-
-                      ]
                   }
                 ]
             }



Mime
View raw message