ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hi...@apache.org
Subject svn commit: r739230 - /ant/ivy/core/trunk/doc/dev/updatesite.html
Date Fri, 30 Jan 2009 10:36:59 GMT
Author: hibou
Date: Fri Jan 30 10:36:59 2009
New Revision: 739230

URL: http://svn.apache.org/viewvc?rev=739230&view=rev
Log:
IVYDE-156: update the release doc so it references the new ant targets

Modified:
    ant/ivy/core/trunk/doc/dev/updatesite.html

Modified: ant/ivy/core/trunk/doc/dev/updatesite.html
URL: http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/dev/updatesite.html?rev=739230&r1=739229&r2=739230&view=diff
==============================================================================
--- ant/ivy/core/trunk/doc/dev/updatesite.html (original)
+++ ant/ivy/core/trunk/doc/dev/updatesite.html Fri Jan 30 10:36:59 2009
@@ -38,27 +38,16 @@
 The update site svn location is there: https://svn.apache.org/repos/asf/ant/ivy/updatesite/trunk
. You will update it so it will contain the new artifacts.
 
 <ul><li>For an <u>Ivy</u> release:
-The new ivy bundle have to be placed in the plugins directory of the updatesite. So you should
do something like:
-<code>cp ..../ivy.jar dist/plugins/org.apache.ivy_$VERSION.jar</code>
-
-Then Eclipse needs a feature, which will be generated at the right place with an ant target:
-<pre>
-ant generate-ivy-feature -Divy.version=$VERSION</pre>
-</li><li>
+As you have a build jar for Ivy, just do:
+<code>ant install-ivy -Divy.jar=...../path/to/ivy.jar</code>
+<li>
 For an <u>IvyDE</u> release:
 The zip distribution needs to be unpacked into the updatesite directory:
-<pre>
-cd dist
-unzip ..../org.apache.ivyde.feature-$VERSION.zip
-</pre>
+<code>ant install-ivyde -Divyde.zip=...../path/to/org.apache.ivyde.feature-${VERSION}.zip</code>
 </li>
 </ul>
 
-Then the deprecated versions of the plugins and the features should be removed.
-
-<h2>Update the site.xml</h2>
-
-The <tt>site.xml</tt> file in the <tt>dist</tt> directory should
be edited so it will reference the new artifacts. You should just change the version number
accordingly to the release.
+Those previous tasks should have deleted some files, but not using the svn command: you should
see some ! in your svn status log. Then do some <tt>svn rm</tt> on those files.
 
 <h2>Prepare the update site</h2>
 



Mime
View raw message