Author: hibou
Date: Sat Apr 26 16:52:13 2014
New Revision: 1590249
URL: http://svn.apache.org/r1590249
Log:
update Ivy site for the doc of trunk
Added:
ant/site/ivy/production/history/trunk/running.html (with props)
Modified:
ant/site/ivy/production/history/trunk/book.html
ant/site/ivy/production/history/trunk/concept.html
ant/site/ivy/production/history/trunk/dev.html
ant/site/ivy/production/history/trunk/dev/makerelease.html
ant/site/ivy/production/history/trunk/reference.html
ant/site/ivy/production/history/trunk/standalone.html
Modified: ant/site/ivy/production/history/trunk/book.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/book.html?rev=1590249&r1=1590248&r2=1590249&view=diff
==============================================================================
--- ant/site/ivy/production/history/trunk/book.html (original)
+++ ant/site/ivy/production/history/trunk/book.html Sat Apr 26 16:52:13 2014
@@ -641,6 +641,8 @@ This part introduces the main concepts u
As the title suggests, here you will find an explanation of how Ivy does work
internally, which can help to better understand and customize its use.
<li><a href="install.html">Installation</a></li>
This part describes how to install Ivy.
+<li>running</li>
+This part describes possibility to control the behavior of Ivy at run time
</ul>
<li><a href="settings.html">Settings Files</a></li>
This part is dedicated to the specification of the settings file of Ivy
(usually called ivysettings.xml). It also gives the list of built-in dependency
resolvers available in Ivy.
@@ -791,6 +793,7 @@ Most of the artifacts found in a reposit
<ul>
<li><tt>zip</tt>, <tt>jar</tt> or <tt>war</tt>: the artifact will be
uncompressed as a folder</li>
<li><tt>pack200</tt>: the artifact will be unpacked to a file via the <a
href="http://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html";>pack200</a>
algorithm</li>
+ <li><tt>bundle</tt>: the OSGi artifact will be uncompressed as a folder,
and every embedded jar file entry which is packed via the the <a
href="http://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html";>pack200</a>
algorithm will be unpacked</li>
</ul>
So, if in an <tt>ivy.xml</tt>, there would be declared a such artifact:
@@ -5343,7 +5346,7 @@ Contrary to ant properties, ivy variable
</tbody>
</table>
- <hr/><div class='toc-title toc-title-3'>Using standalone</div><br
class="xooki-br"/>Ivy can be used as a standalone program very easily. All you
need is a java 1.4+ runtime environment (JRE)!<br class="xooki-br"/><br
class="xooki-br"/>Then here is how to call it:
+ <hr/><div class='toc-title toc-title-3'>Using standalone</div><br
class="xooki-br"/>Ivy can be used as a standalone program very easily. All you
need is a Java 5+ runtime environment (JRE)!<br class="xooki-br"/><br
class="xooki-br"/>Then here is how to call it:
<pre>
java -jar ivy.jar -?
</pre>
@@ -5664,8 +5667,8 @@ All you need is
<em>We recommend either ant 1.6.5 or 1.7.0</em>
<li><a href="http://junit.org";>junit</a> 3.8.2 jar in your ant lib</li>
<em> this is not required if you use ant 1.7</em>
-<li>a <a href="http://java.sun.com/";>jdk</a> 1.4 or greater</li>
-<em>Build instructions have been successfully tested with sun jdk 1.4.2, 1.5.0
and 1.6.0</em>
+<li>a <a href="http://java.sun.com/";>jdk</a> 1.5 or greater</li>
+<em>Build instructions have been successfully tested with sun jdk 1.5.0 and
1.6.0</em>
</ul>
<h2>Procedure</h2>
@@ -5712,12 +5715,12 @@ The Ivy project comes with settings for
Before trying to implement your own, we encourage you to check if the solution
to your problem cannot be addressed by existing features, or by contributed
ones. Do not hesitate to ask for help on the mailing-lists.<br
class="xooki-br"/><br class="xooki-br"/>If you still don't find what you need,
then you'll have to develop your own plugin or find someone who could do that
for you.<br class="xooki-br"/><br class="xooki-br"/>All ivy plug-ins use the
same code patterns as ant specific tasks for parameters. This means that if you
want to have a "myattribute" of type String, you just have to declare a method
called setMyattribute(String val) on your plug-in. The same applies to child
tags, you just have to follow Ant specifications.<br class="xooki-br"/><br
class="xooki-br"/>All pluggable code in Ivy is located in the <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins";>org.apache.ivy.plugins</a>
package. In each package you will find an interface
that you must implement to provide a new plugin. We usually also provide an
abstract class easing the implementation and making your code more independent
of interface changes. We heavily recommend using these abstract classes as a
base class.<br class="xooki-br"/><br class="xooki-br"/>To understand how your
implementation can be done, we suggest looking at existing implementations we
provide, it's the best way to get started.<br class="xooki-br"/> <hr/><div
class='toc-title toc-title-3'>Making a release</div><br
class="xooki-br"/><h1>Making a release</h1>
<h2>Requirements</h2>
-Requirements for making a release are similar to the requirements for building
from source, except that sun jdk 1.6 and ant 1.7 are required.<br
class="xooki-br"/><h2>Procedure</h2>
+Requirements for making a release are similar to the requirements for building
from source, except that JDK 1.6+ and Apache Ant 1.9+ are required.<br
class="xooki-br"/><h2>Procedure</h2>
<h3>1. Check the files which needs to be updated for the release.</h3>
On the trunk, check that files which require update for the release are up to
date.<br class="xooki-br"/>This includes particularly:<br
class="xooki-br"/>RELEASE_NOTES<br class="xooki-br"/>CHANGES<br
class="xooki-br"/>README<br class="xooki-br"/><h3>2. Create a release
branch</h3>
-This will allow to work separately from other developers, in case you need any
last modification.
+This will allow to work separately from other developers, in case you need any
last modification. For a release we have 2 branches. For instance, suppose we
create a 2.0.0-beta1 release. We have a branch for the code for all 2.0.x
releases, this is the '2.0.x' branch. From this branch we will create the
release branch which is for a specific release. It is possible that the 2.0.x
branch has already been created when releasing a previous version, in that case
the creation of this branch can be skipped.
<pre>
-svn copy <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk";>https://svn.apache.org/repos/asf/ant/ivy/core/trunk</a>
\<br class="xooki-br"/> <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1</a>
\<br class="xooki-br"/> -m "Creating a release branch for 2.0.0-beta1."
+svn copy <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk";>https://svn.apache.org/repos/asf/ant/ivy/core/trunk</a>
\<br class="xooki-br"/> <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x</a>
\<br class="xooki-br"/> -m "Creating a 2.0.x branch."<br
class="xooki-br"/>svn copy <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x</a>
\<br class="xooki-br"/> <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1</a>
\<br class="xooki-br"/> -m "Creating a release branch for 2.0.0-beta1."
</pre>
<h3>3. Check out the branch</h3>
<pre>
@@ -5753,12 +5756,7 @@ Here is a ruby script you can use to sig
<pre>
require 'find'<br class="xooki-br"/><br
class="xooki-br"/>Find.find('build/distrib') do |f| <br class="xooki-br"/>
`gpg --armor --output #{f}.asc --detach-sig #{f}` if File.file?(f) && ['.zip',
'.gz', '.jar', '.pom'].include?(File.extname(f))<br class="xooki-br"/>end
</pre>
-Be prepared to enter your passphrase several times if you use this script, gpg
will ask for your passphrase for each file to sign.<br class="xooki-br"/><br
class="xooki-br"/>When you're done upload the content of the distrib directory
to a publicly accessible web site, your apache personal site being a good
location for this. Make sure you include some kind of disclaimer somewhere to
inform people the release is not approved yet.<br class="xooki-br"/><br
class="xooki-br"/>You can for example add a HEADER.html like this:
-<pre>
-<h2>WARNING: files available here are NOT an Apache approved release
yet.</h2>
-</pre>
-
-<h3>11. Prepare the Eclipse update site</h3>
+Be prepared to enter your passphrase several times if you use this script, gpg
will ask for your passphrase for each file to sign.<br class="xooki-br"/><br
class="xooki-br"/><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="http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html";>that
page</a> to know how to process.<br class="xooki-br"/><br
class="xooki-br"/><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
@@ -5773,23 +5771,19 @@ xooki -r790212 <a href="https://svn.apac
And commit that modification.<br class="xooki-br"/><br
class="xooki-br"/><h3>Publish the release candidate</h3>
-<ul>Two choices here:<br class="xooki-br"/> <li>commit them into the dev dist
area: <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a>
</li>
- <li>or simply put it in your <tt>public_html</tt> folder on
people.apache.org so it will be avalaible at <a
href="http://people.apache.org/~$LOGIN/$RELEASENAME";>http://people.apache.org/~$LOGIN/$RELEASENAME</a>
</li>
-</ul>
-
-<h3>13. Call for a vote to approve the release</h3>
+All artifacts in <tt>build/distrib</tt> except the <tt>maven2</tt> folder
needs to be published on the 'dist' svn of the ASF, in the <b>dev</b> part.<br
class="xooki-br"/><br class="xooki-br"/>The artifacts should be pushed in that
svn folder: <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a><br
class="xooki-br"/><br class="xooki-br"/><h3>13. Call for a vote to approve the
release</h3>
Cast a vote to approve the release on the [email protected] mailing list.<br
class="xooki-br"/><br class="xooki-br"/>Here is an example:
<pre>
-Subject: [VOTE] Ivy ${version} Release<br class="xooki-br"/><br
class="xooki-br"/>I have built a release candidate for Ivy ${version}<br
class="xooki-br"/><br class="xooki-br"/>You can download it from this URL:
${url}<br class="xooki-br"/><br class="xooki-br"/>Do you vote for the release
of these binaries?<br class="xooki-br"/><br class="xooki-br"/>[ ] Yes<br
class="xooki-br"/>[ ] No<br class="xooki-br"/><br class="xooki-br"/>Regards,<br
class="xooki-br"/><br class="xooki-br"/>${me}, Ivy ${version} release manager
+Subject: [VOTE] Ivy ${version} Release<br class="xooki-br"/><br
class="xooki-br"/>I have built a release candidate for Ivy ${version}<br
class="xooki-br"/><br class="xooki-br"/>The svn tag of this release is: <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/tags/${version}@${svn-rev-of-the-tag";>https://svn.apache.org/repos/asf/ant/ivy/core/tags/${version}@${svn-rev-of-the-tag</a>}<br
class="xooki-br"/><br class="xooki-br"/>The artifacts has been published to:
<a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION@${svn-rev-of-the-check-in";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION@${svn-rev-of-the-check-in</a>}<br
class="xooki-br"/><br class="xooki-br"/>Do you vote for the release of these
binaries?<br class="xooki-br"/><br class="xooki-br"/>[ ] Yes<br
class="xooki-br"/>[ ] No<br class="xooki-br"/><br class="xooki-br"/>Regards,<br
class="xooki-br"/><br class="xooki-br"/>${me}, Ivy ${version} release manager
</pre>
<h3>14. Publish the release</h3>
-If the release is approved, it's now time to make it public. The apache dist
is manage by svnpubsub, so releases should be committed into <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a><br
class="xooki-br"/><br class="xooki-br"/>If the release candidate has been
staged into the dev area, then just do:
+If the release is approved, it's now time to make it public. The artifacts in
the <i>dev</i> part needs to be moved into the <i>release</i> one:
<pre>
$ svn mv <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a>
<a
href="https://dist.apache.org/repos/dist/release/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/release/ant/ivy/$VERSION</a>
</pre>
-If the candidate has been published on people.apache.org, just directly commit
the artifacts into the subversion repository <a
href="https://dist.apache.org/repos/dist/release/ant/";>https://dist.apache.org/repos/dist/release/ant/</a>
<br class="xooki-br"/><br class="xooki-br"/>In order to keep the main dist
area of a reasonable size, old releases should be removed. They will disapear
from the main dist but will still be available via the <a
href="http://archive.apache.org/dist/ant/ivy/";>archive</a>. To do so, just use
the <tt>svn rm</tt> command against the artifacts or folders to remove.<br
class="xooki-br"/><br class="xooki-br"/><h3>15. Update the web site</h3>
+In order to keep the main dist area of a reasonable size, old releases should
be removed. They will disapear from the main dist but will still be available
via the <a href="http://archive.apache.org/dist/ant/ivy/";>archive</a>. To do
so, just use the <tt>svn rm</tt> command against the artifacts or folders to
remove.<br class="xooki-br"/><br class="xooki-br"/><h3>15. Update the web
site</h3>
Add a link to the released version documentation in the web site. <br
class="xooki-br"/><br class="xooki-br"/>To do so, you need to:<br
class="xooki-br"/><ol>
<li>add a svn externals reference to the documentation</li>
edit the svn properties of site/history, and in the svn:externals property,
add a line like this one:
Modified: ant/site/ivy/production/history/trunk/concept.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/concept.html?rev=1590249&r1=1590248&r2=1590249&view=diff
==============================================================================
--- ant/site/ivy/production/history/trunk/concept.html (original)
+++ ant/site/ivy/production/history/trunk/concept.html Sat Apr 26 16:52:13 2014
@@ -337,6 +337,7 @@ Most of the artifacts found in a reposit
<ul>
<li><tt>zip</tt>, <tt>jar</tt> or <tt>war</tt>: the artifact will be
uncompressed as a folder</li>
<li><tt>pack200</tt>: the artifact will be unpacked to a file via the <a
href="http://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html";>pack200</a>
algorithm</li>
+ <li><tt>bundle</tt>: the OSGi artifact will be uncompressed as a folder,
and every embedded jar file entry which is packed via the the <a
href="http://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html";>pack200</a>
algorithm will be unpacked</li>
</ul>
So, if in an <tt>ivy.xml</tt>, there would be declared a such artifact:
Modified: ant/site/ivy/production/history/trunk/dev.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/dev.html?rev=1590249&r1=1590248&r2=1590249&view=diff
==============================================================================
--- ant/site/ivy/production/history/trunk/dev.html (original)
+++ ant/site/ivy/production/history/trunk/dev.html Sat Apr 26 16:52:13 2014
@@ -247,8 +247,8 @@ All you need is
<em>We recommend either ant 1.6.5 or 1.7.0</em>
<li><a href="http://junit.org";>junit</a> 3.8.2 jar in your ant lib</li>
<em> this is not required if you use ant 1.7</em>
-<li>a <a href="http://java.sun.com/";>jdk</a> 1.4 or greater</li>
-<em>Build instructions have been successfully tested with sun jdk 1.4.2, 1.5.0
and 1.6.0</em>
+<li>a <a href="http://java.sun.com/";>jdk</a> 1.5 or greater</li>
+<em>Build instructions have been successfully tested with sun jdk 1.5.0 and
1.6.0</em>
</ul>
<h2>Procedure</h2>
Modified: ant/site/ivy/production/history/trunk/dev/makerelease.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/dev/makerelease.html?rev=1590249&r1=1590248&r2=1590249&view=diff
==============================================================================
--- ant/site/ivy/production/history/trunk/dev/makerelease.html (original)
+++ ant/site/ivy/production/history/trunk/dev/makerelease.html Sat Apr 26
16:52:13 2014
@@ -239,12 +239,12 @@
<h1 class="title">Making a release</h1>
<br class="xooki-br"/><h1>Making a release</h1>
<h2>Requirements</h2>
-Requirements for making a release are similar to the requirements for building
from source, except that sun jdk 1.6 and ant 1.7 are required.<br
class="xooki-br"/><h2>Procedure</h2>
+Requirements for making a release are similar to the requirements for building
from source, except that JDK 1.6+ and Apache Ant 1.9+ are required.<br
class="xooki-br"/><h2>Procedure</h2>
<h3>1. Check the files which needs to be updated for the release.</h3>
On the trunk, check that files which require update for the release are up to
date.<br class="xooki-br"/>This includes particularly:<br
class="xooki-br"/>RELEASE_NOTES<br class="xooki-br"/>CHANGES<br
class="xooki-br"/>README<br class="xooki-br"/><h3>2. Create a release
branch</h3>
-This will allow to work separately from other developers, in case you need any
last modification.
+This will allow to work separately from other developers, in case you need any
last modification. For a release we have 2 branches. For instance, suppose we
create a 2.0.0-beta1 release. We have a branch for the code for all 2.0.x
releases, this is the '2.0.x' branch. From this branch we will create the
release branch which is for a specific release. It is possible that the 2.0.x
branch has already been created when releasing a previous version, in that case
the creation of this branch can be skipped.
<pre>
-svn copy <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk";>https://svn.apache.org/repos/asf/ant/ivy/core/trunk</a>
\<br class="xooki-br"/> <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1</a>
\<br class="xooki-br"/> -m "Creating a release branch for 2.0.0-beta1."
+svn copy <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/trunk";>https://svn.apache.org/repos/asf/ant/ivy/core/trunk</a>
\<br class="xooki-br"/> <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x</a>
\<br class="xooki-br"/> -m "Creating a 2.0.x branch."<br
class="xooki-br"/>svn copy <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.x</a>
\<br class="xooki-br"/> <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1";>https://svn.apache.org/repos/asf/ant/ivy/core/branches/2.0.0-beta1</a>
\<br class="xooki-br"/> -m "Creating a release branch for 2.0.0-beta1."
</pre>
<h3>3. Check out the branch</h3>
<pre>
@@ -280,12 +280,7 @@ Here is a ruby script you can use to sig
<pre>
require 'find'<br class="xooki-br"/><br
class="xooki-br"/>Find.find('build/distrib') do |f| <br class="xooki-br"/>
`gpg --armor --output #{f}.asc --detach-sig #{f}` if File.file?(f) && ['.zip',
'.gz', '.jar', '.pom'].include?(File.extname(f))<br class="xooki-br"/>end
</pre>
-Be prepared to enter your passphrase several times if you use this script, gpg
will ask for your passphrase for each file to sign.<br class="xooki-br"/><br
class="xooki-br"/>When you're done upload the content of the distrib directory
to a publicly accessible web site, your apache personal site being a good
location for this. Make sure you include some kind of disclaimer somewhere to
inform people the release is not approved yet.<br class="xooki-br"/><br
class="xooki-br"/>You can for example add a HEADER.html like this:
-<pre>
-<h2>WARNING: files available here are NOT an Apache approved release
yet.</h2>
-</pre>
-
-<h3>11. Prepare the Eclipse update site</h3>
+Be prepared to enter your passphrase several times if you use this script, gpg
will ask for your passphrase for each file to sign.<br class="xooki-br"/><br
class="xooki-br"/><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="http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html";>that
page</a> to know how to process.<br class="xooki-br"/><br
class="xooki-br"/><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
@@ -300,23 +295,19 @@ xooki -r790212 <a href="https://svn.apac
And commit that modification.<br class="xooki-br"/><br
class="xooki-br"/><h3>Publish the release candidate</h3>
-<ul>Two choices here:<br class="xooki-br"/> <li>commit them into the dev dist
area: <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a>
</li>
- <li>or simply put it in your <tt>public_html</tt> folder on
people.apache.org so it will be avalaible at <a
href="http://people.apache.org/~$LOGIN/$RELEASENAME";>http://people.apache.org/~$LOGIN/$RELEASENAME</a>
</li>
-</ul>
-
-<h3>13. Call for a vote to approve the release</h3>
+All artifacts in <tt>build/distrib</tt> except the <tt>maven2</tt> folder
needs to be published on the 'dist' svn of the ASF, in the <b>dev</b> part.<br
class="xooki-br"/><br class="xooki-br"/>The artifacts should be pushed in that
svn folder: <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a><br
class="xooki-br"/><br class="xooki-br"/><h3>13. Call for a vote to approve the
release</h3>
Cast a vote to approve the release on the [email protected] mailing list.<br
class="xooki-br"/><br class="xooki-br"/>Here is an example:
<pre>
-Subject: [VOTE] Ivy ${version} Release<br class="xooki-br"/><br
class="xooki-br"/>I have built a release candidate for Ivy ${version}<br
class="xooki-br"/><br class="xooki-br"/>You can download it from this URL:
${url}<br class="xooki-br"/><br class="xooki-br"/>Do you vote for the release
of these binaries?<br class="xooki-br"/><br class="xooki-br"/>[ ] Yes<br
class="xooki-br"/>[ ] No<br class="xooki-br"/><br class="xooki-br"/>Regards,<br
class="xooki-br"/><br class="xooki-br"/>${me}, Ivy ${version} release manager
+Subject: [VOTE] Ivy ${version} Release<br class="xooki-br"/><br
class="xooki-br"/>I have built a release candidate for Ivy ${version}<br
class="xooki-br"/><br class="xooki-br"/>The svn tag of this release is: <a
href="https://svn.apache.org/repos/asf/ant/ivy/core/tags/${version}@${svn-rev-of-the-tag";>https://svn.apache.org/repos/asf/ant/ivy/core/tags/${version}@${svn-rev-of-the-tag</a>}<br
class="xooki-br"/><br class="xooki-br"/>The artifacts has been published to:
<a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION@${svn-rev-of-the-check-in";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION@${svn-rev-of-the-check-in</a>}<br
class="xooki-br"/><br class="xooki-br"/>Do you vote for the release of these
binaries?<br class="xooki-br"/><br class="xooki-br"/>[ ] Yes<br
class="xooki-br"/>[ ] No<br class="xooki-br"/><br class="xooki-br"/>Regards,<br
class="xooki-br"/><br class="xooki-br"/>${me}, Ivy ${version} release manager
</pre>
<h3>14. Publish the release</h3>
-If the release is approved, it's now time to make it public. The apache dist
is manage by svnpubsub, so releases should be committed into <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a><br
class="xooki-br"/><br class="xooki-br"/>If the release candidate has been
staged into the dev area, then just do:
+If the release is approved, it's now time to make it public. The artifacts in
the <i>dev</i> part needs to be moved into the <i>release</i> one:
<pre>
$ svn mv <a
href="https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION</a>
<a
href="https://dist.apache.org/repos/dist/release/ant/ivy/$VERSION";>https://dist.apache.org/repos/dist/release/ant/ivy/$VERSION</a>
</pre>
-If the candidate has been published on people.apache.org, just directly commit
the artifacts into the subversion repository <a
href="https://dist.apache.org/repos/dist/release/ant/";>https://dist.apache.org/repos/dist/release/ant/</a>
<br class="xooki-br"/><br class="xooki-br"/>In order to keep the main dist
area of a reasonable size, old releases should be removed. They will disapear
from the main dist but will still be available via the <a
href="http://archive.apache.org/dist/ant/ivy/";>archive</a>. To do so, just use
the <tt>svn rm</tt> command against the artifacts or folders to remove.<br
class="xooki-br"/><br class="xooki-br"/><h3>15. Update the web site</h3>
+In order to keep the main dist area of a reasonable size, old releases should
be removed. They will disapear from the main dist but will still be available
via the <a href="http://archive.apache.org/dist/ant/ivy/";>archive</a>. To do
so, just use the <tt>svn rm</tt> command against the artifacts or folders to
remove.<br class="xooki-br"/><br class="xooki-br"/><h3>15. Update the web
site</h3>
Add a link to the released version documentation in the web site. <br
class="xooki-br"/><br class="xooki-br"/>To do so, you need to:<br
class="xooki-br"/><ol>
<li>add a svn externals reference to the documentation</li>
edit the svn properties of site/history, and in the svn:externals property,
add a line like this one:
Modified: ant/site/ivy/production/history/trunk/reference.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/reference.html?rev=1590249&r1=1590248&r2=1590249&view=diff
==============================================================================
--- ant/site/ivy/production/history/trunk/reference.html (original)
+++ ant/site/ivy/production/history/trunk/reference.html Sat Apr 26 16:52:13
2014
@@ -250,6 +250,8 @@ This part introduces the main concepts u
As the title suggests, here you will find an explanation of how Ivy does work
internally, which can help to better understand and customize its use.
<li><a href="install.html">Installation</a></li>
This part describes how to install Ivy.
+<li>running</li>
+This part describes possibility to control the behavior of Ivy at run time
</ul>
<li><a href="settings.html">Settings Files</a></li>
This part is dedicated to the specification of the settings file of Ivy
(usually called ivysettings.xml). It also gives the list of built-in dependency
resolvers available in Ivy.
Added: ant/site/ivy/production/history/trunk/running.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/running.html?rev=1590249&view=auto
==============================================================================
--- ant/site/ivy/production/history/trunk/running.html (added)
+++ ant/site/ivy/production/history/trunk/running.html Sat Apr 26 16:52:13 2014
@@ -0,0 +1,270 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd";>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<html>
+<head>
+ <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+ <script type="text/javascript">var xookiConfig = {level: 0};</script>
+
+
+<title>Documentation (trunk) | Apache Ivy™</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+ <link rel="stylesheet" type="text/css" href="style/style.css" />
+ <script src="js/jquery.pack.js" type="text/javascript"></script>
+ <script src="js/jquery.treeview.js" type="text/javascript"></script>
+ <script type="text/javascript">
+ $(document).ready(function(){$("#treemenu").Treeview({speed: "fast",store:
true});});
+ </script>
+
+<script language="javascript" type="text/javascript">xooki = {u: function(url)
{return "xooki/"+url;}};</script>
+</head>
+<body>
+
+<div id="body">
+<table id="header" summary="Navigation elements." border="0"
+ cellpadding="0" cellspacing="0" width="100%">
+ <tr>
+ <td id="home" width="30%"><a href="http://ant.apache.org/";
+ title="Apache Ant"><img src="images/ant-group-logo.gif"
alt="Apache Ant"
+ border="0" /></a></td>
+
+ <td class="product" width="70%" align="right"
valign="middle"><img
+ src="images/logo.png" alt="ivy" border="0" /></td>
+ </tr>
+</table>
+
+<table id="top-menu" summary="Navigation elements." border="0"
+ cellpadding="0" cellspacing="0" width="100%">
+ <tr>
+ <td>
+
+ <div style="float:right;margin: 0 10px;">
+ <!-- Google CSE Search Box Begins -->
+ <form id="searchbox_014292259695392975429:5y6qypnrni8"
action="http://ant.apache.org/ivy/search.html";>
+ <input type="hidden" name="cx" value="014292259695392975429:5y6qypnrni8" />
+ <input type="hidden" name="cof" value="FORID:11" />
+ <input name="q" type="text" size="30" />
+ <input type="submit" name="sa" value="Search" />
+ </form>
+ <script type="text/javascript"
src="http://www.google.com/coop/cse/brand?form=searchbox_014292259695392975429%3A5y6qypnrni8";></script>
+<!-- Google CSE Search Box Ends -->
+ </div>
+
+ <div id="navcontainer">
+ <a href="http://www.apache.org/";>Apache™</a> > <a
href="http://ant.apache.org/";>Apache Ant™</a> > <a
href="http://ant.apache.org/ivy/";>Apache Ivy™</a> > <span
class="breadCrumb"><a href="index.html" class="current">Documentation
(trunk)</a></span>
+ </div>
+ </td>
+ </tr>
+
+</table>
+
+<table id="content" border="0" cellpadding="0" cellspacing="0"
+ width="100%">
+ <tr>
+ <td id="sidebar-left">
+ <div class="block block-book" id="block-book-0">
+ <h2>Apache Ivy™</h2>
+
+ <div class="content"><ul id="treemenu" class="treeview">
+<li id="xooki-index" class="submenu"><a href="index.html"
class="current">Documentation (trunk)</a><ul class="open"><li
id="xooki-tutorial" class="submenu"><a href="tutorial.html" >Tutorials</a><ul
class="closed"><li id="xooki-tutorial/start"><a href="tutorial/start.html"
>Quick Start</a></li>
+<li id="xooki-tutorial/defaultconf"><a href="tutorial/defaultconf.html"
>Adjusting default settings</a></li>
+<li id="xooki-tutorial/multiple"><a href="tutorial/multiple.html" >Multiple
Resolvers</a></li>
+<li id="xooki-tutorial/dual"><a href="tutorial/dual.html" >Dual
Resolver</a></li>
+<li id="xooki-tutorial/dependence"><a href="tutorial/dependence.html" >Project
dependencies</a></li>
+<li id="xooki-tutorial/multiproject"><a href="tutorial/multiproject.html"
>Using Ivy in multiple projects environment</a></li>
+<li id="xooki-tutorial/conf"><a href="tutorial/conf.html" >Using Ivy Module
Configurations</a></li>
+<li id="xooki-tutorial/build-repository" class="submenu"><a
href="tutorial/build-repository.html" >Building a repository</a><ul
class="closed"><li id="xooki-tutorial/build-repository/basic"><a
href="tutorial/build-repository/basic.html" >Basic repository copy</a></li>
+<li id="xooki-tutorial/build-repository/advanced"><a
href="tutorial/build-repository/advanced.html" >Using namespaces</a></li>
+</ul></li>
+<li id="xooki-moreexamples"><a href="moreexamples.html" >More examples</a></li>
+</ul></li>
+<li id="xooki-reference" class="submenu"><a href="reference.html"
>Reference</a><ul class="closed"><li id="xooki-intro"
class="submenu">Introduction<ul class="closed"><li id="xooki-terminology"><a
href="terminology.html" >Terminology</a></li>
+<li id="xooki-concept"><a href="concept.html" >Main Concepts</a></li>
+<li id="xooki-textual"><a href="textual.html" >Text Conventions</a></li>
+<li id="xooki-principle"><a href="principle.html" >How does it work ?</a></li>
+<li id="xooki-bestpractices"><a href="bestpractices.html" >Best
practices</a></li>
+<li id="xooki-compatibility"><a href="compatibility.html"
>Compatibility</a></li>
+<li id="xooki-install"><a href="install.html" >Installation</a></li>
+</ul></li>
+<li id="xooki-settings" class="submenu"><a href="settings.html" >Settings
Files</a><ul class="closed"><li id="xooki-settings/property"><a
href="settings/property.html" >property</a></li>
+<li id="xooki-settings/properties"><a href="settings/properties.html"
>properties</a></li>
+<li id="xooki-settings/settings"><a href="settings/settings.html"
>settings</a></li>
+<li id="xooki-settings/include"><a href="settings/include.html"
>include</a></li>
+<li id="xooki-settings/classpath"><a href="settings/classpath.html"
>classpath</a></li>
+<li id="xooki-settings/typedef"><a href="settings/typedef.html"
>typedef</a></li>
+<li id="xooki-settings/credentials"><a href="settings/credentials.html"
>credentials</a></li>
+<li id="xooki-settings/signers"><a href="settings/signers.html"
>signers</a></li>
+<li id="xooki-settings/lock-strategies"><a
href="settings/lock-strategies.html" >lock-strategies</a></li>
+<li id="xooki-settings/caches" class="submenu"><a href="settings/caches.html"
>caches</a><ul class="closed"><li id="xooki-settings/caches/cache"
class="submenu"><a href="settings/caches/cache.html" >cache</a><ul
class="closed"><li id="xooki-settings/caches/ttl"><a
href="settings/caches/ttl.html" >ttl</a></li>
+</ul></li>
+</ul></li>
+<li id="xooki-settings/latest-strategies"><a
href="settings/latest-strategies.html" >latest-strategies</a></li>
+<li id="xooki-settings/parsers"><a href="settings/parsers.html"
>parsers</a></li>
+<li id="xooki-settings/namespaces" class="submenu"><a
href="settings/namespaces.html" >namespaces</a><ul class="closed"><li
id="xooki-settings/namespace" class="submenu"><a href="settings/namespace.html"
>namespace</a><ul class="closed"><li id="xooki-settings/namespace/rule"
class="submenu"><a href="settings/namespace/rule.html" >rule</a><ul
class="closed"><li id="xooki-settings/namespace/fromtosystem"
class="submenu"><a href="settings/namespace/fromtosystem.html" >fromsystem /
tosystem</a><ul class="closed"><li id="xooki-settings/namespace/src"><a
href="settings/namespace/src.html" >src</a></li>
+<li id="xooki-settings/namespace/dest"><a href="settings/namespace/dest.html"
>dest</a></li>
+</ul></li>
+</ul></li>
+</ul></li>
+</ul></li>
+<li id="xooki-settings/macrodef" class="submenu"><a
href="settings/macrodef.html" >macrodef</a><ul class="closed"><li
id="xooki-settings/macrodef/attribute"><a
href="settings/macrodef/attribute.html" >attribute</a></li>
+</ul></li>
+<li id="xooki-settings/resolvers" class="submenu"><a
href="settings/resolvers.html" >resolvers</a><ul class="closed"><li
id="xooki-resolver/ivyrep"><a href="resolver/ivyrep.html" >IvyRep
Resolver</a></li>
+<li id="xooki-resolver/ibiblio"><a href="resolver/ibiblio.html" >IBiblio
Resolver</a></li>
+<li id="xooki-resolver/packager"><a href="resolver/packager.html" >Packager
resolver</a></li>
+<li id="xooki-resolver/filesystem"><a href="resolver/filesystem.html" >File
System resolver</a></li>
+<li id="xooki-resolver/url"><a href="resolver/url.html" >Url Resolver</a></li>
+<li id="xooki-resolver/chain"><a href="resolver/chain.html" >Chain
Resolver</a></li>
+<li id="xooki-resolver/dual"><a href="resolver/dual.html" >Dual
resolver</a></li>
+<li id="xooki-resolver/sftp"><a href="resolver/sftp.html" >sftp
resolver</a></li>
+<li id="xooki-resolver/ssh"><a href="resolver/ssh.html" >ssh resolver</a></li>
+<li id="xooki-resolver/vfs"><a href="resolver/vfs.html" >vfs resolver</a></li>
+<li id="xooki-resolver/jar"><a href="resolver/jar.html" >Jar resolver</a></li>
+<li id="xooki-resolver/obr"><a href="resolver/obr.html" >OSGi Bundle
Repository</a></li>
+<li id="xooki-resolver/osgiagg"><a href="resolver/osgiagg.html" >Aggregated
OSGi Repository</a></li>
+<li id="xooki-resolver/updatesite"><a href="resolver/updatesite.html" >Eclipse
updatesite</a></li>
+<li id="xooki-resolver/mirrored"><a href="resolver/mirrored.html" >Mirrored
Resolver</a></li>
+</ul></li>
+<li id="xooki-settings/conflict-managers"><a
href="settings/conflict-managers.html" >conflict-managers</a></li>
+<li id="xooki-settings/modules" class="submenu"><a
href="settings/modules.html" >modules</a><ul class="closed"><li
id="xooki-settings/module"><a href="settings/module.html" >module</a></li>
+</ul></li>
+<li id="xooki-settings/outputters"><a href="settings/outputters.html"
>outputters</a></li>
+<li id="xooki-settings/signers"><a href="settings/signers.html"
>signers</a></li>
+<li id="xooki-settings/statuses" class="submenu"><a
href="settings/statuses.html" >statuses</a><ul class="closed"><li
id="xooki-settings/status"><a href="settings/status.html" >status</a></li>
+</ul></li>
+<li id="xooki-settings/triggers"><a href="settings/triggers.html"
>triggers</a></li>
+<li id="xooki-settings/version-matchers"><a
href="settings/version-matchers.html" >version-matchers</a></li>
+</ul></li>
+<li id="xooki-ivyfile" class="submenu"><a href="ivyfile.html" >Ivy
Files</a><ul class="closed"><li id="xooki-ivyfile/info" class="submenu"><a
href="ivyfile/info.html" >info</a><ul class="closed"><li
id="xooki-ivyfile/extends"><a href="ivyfile/extends.html" >extends</a></li>
+<li id="xooki-ivyfile/license"><a href="ivyfile/license.html" >license</a></li>
+<li id="xooki-ivyfile/ivyauthor"><a href="ivyfile/ivyauthor.html"
>ivyauthor</a></li>
+<li id="xooki-ivyfile/repository"><a href="ivyfile/repository.html"
>repository</a></li>
+<li id="xooki-ivyfile/description"><a href="ivyfile/description.html"
>description</a></li>
+</ul></li>
+<li id="xooki-ivyfile/configurations" class="submenu"><a
href="ivyfile/configurations.html" >configurations</a><ul class="closed"><li
id="xooki-ivyfile/conf"><a href="ivyfile/conf.html" >conf</a></li>
+<li id="xooki-ivyfile/include"><a href="ivyfile/include.html" >include</a></li>
+</ul></li>
+<li id="xooki-ivyfile/publications" class="submenu"><a
href="ivyfile/publications.html" >publications</a><ul class="closed"><li
id="xooki-ivyfile/artifact" class="submenu"><a href="ivyfile/artifact.html"
>artifact</a><ul class="closed"><li id="xooki-ivyfile/artifact-conf"><a
href="ivyfile/artifact-conf.html" >conf</a></li>
+</ul></li>
+</ul></li>
+<li id="xooki-ivyfile/dependencies" class="submenu"><a
href="ivyfile/dependencies.html" >dependencies</a><ul class="closed"><li
id="xooki-ivyfile/dependency" class="submenu"><a href="ivyfile/dependency.html"
>dependency</a><ul class="closed"><li id="xooki-ivyfile/dependency-conf"
class="submenu"><a href="ivyfile/dependency-conf.html" >conf</a><ul
class="closed"><li id="xooki-ivyfile/mapped"><a href="ivyfile/mapped.html"
>mapped</a></li>
+</ul></li>
+<li id="xooki-ivyfile/dependency-artifact" class="submenu"><a
href="ivyfile/dependency-artifact.html" >artifact</a><ul class="closed"><li
id="xooki-ivyfile/dependency-artifact-conf"><a
href="ivyfile/dependency-artifact-conf.html" >conf</a></li>
+</ul></li>
+<li id="xooki-ivyfile/artifact-exclude" class="submenu"><a
href="ivyfile/artifact-exclude.html" >exclude</a><ul class="closed"><li
id="xooki-ivyfile/artifact-exclude-conf"><a
href="ivyfile/artifact-exclude-conf.html" >conf</a></li>
+</ul></li>
+<li id="xooki-ivyfile/dependency-include" class="submenu"><a
href="ivyfile/dependency-include.html" >include</a><ul class="closed"><li
id="xooki-ivyfile/dependency-include-conf"><a
href="ivyfile/dependency-include-conf.html" >conf</a></li>
+</ul></li>
+</ul></li>
+<li id="xooki-ivyfile/exclude"><a href="ivyfile/exclude.html" >exclude</a></li>
+<li id="xooki-ivyfile/override"><a href="ivyfile/override.html"
>override</a></li>
+<li id="xooki-ivyfile/conflict"><a href="ivyfile/conflict.html"
>conflict</a></li>
+</ul></li>
+<li id="xooki-ivyfile/conflicts" class="submenu"><a
href="ivyfile/conflicts.html" >conflicts</a><ul class="closed"><li
id="xooki-ivyfile/manager"><a href="ivyfile/manager.html" >manager</a></li>
+</ul></li>
+</ul></li>
+<li id="xooki-ant" class="submenu"><a href="ant.html" >Ant Tasks</a><ul
class="closed"><li id="xooki-use/artifactproperty"><a
href="use/artifactproperty.html" >artifactproperty</a></li>
+<li id="xooki-use/artifactreport"><a href="use/artifactreport.html"
>artifactreport</a></li>
+<li id="xooki-use/buildlist"><a href="use/buildlist.html" >buildlist</a></li>
+<li id="xooki-use/buildobr"><a href="use/buildobr.html" >buildobr</a></li>
+<li id="xooki-use/buildnumber"><a href="use/buildnumber.html"
>buildnumber</a></li>
+<li id="xooki-use/cachefileset"><a href="use/cachefileset.html"
>cachefileset</a></li>
+<li id="xooki-use/cachepath"><a href="use/cachepath.html" >cachepath</a></li>
+<li id="xooki-use/checkdepsupdate"><a href="use/checkdepsupdate.html"
>checkdepsupdate</a></li>
+<li id="xooki-use/cleancache"><a href="use/cleancache.html"
>cleancache</a></li>
+<li id="xooki-use/configure"><a href="use/configure.html" >configure</a></li>
+<li id="xooki-use/convertmanifest"><a href="use/convertmanifest.html"
>convertmanifest</a></li>
+<li id="xooki-use/convertpom"><a href="use/convertpom.html"
>convertpom</a></li>
+<li id="xooki-use/deliver"><a href="use/deliver.html" >deliver</a></li>
+<li id="xooki-use/dependencytree"><a href="use/dependencytree.html"
>dependencytree</a></li>
+<li id="xooki-use/findrevision"><a href="use/findrevision.html"
>findrevision</a></li>
+<li id="xooki-use/fixdeps"><a href="use/fixdeps.html" >fixdeps</a></li>
+<li id="xooki-use/info"><a href="use/info.html" >info</a></li>
+<li id="xooki-use/install"><a href="use/install.html" >install</a></li>
+<li id="xooki-use/listmodules"><a href="use/listmodules.html"
>listmodules</a></li>
+<li id="xooki-use/makepom"><a href="use/makepom.html" >makepom</a></li>
+<li id="xooki-use/postresolvetask"><a href="use/postresolvetask.html" >post
resolve tasks</a></li>
+<li id="xooki-use/publish"><a href="use/publish.html" >publish</a></li>
+<li id="xooki-use/repreport"><a href="use/repreport.html" >repreport</a></li>
+<li id="xooki-use/resolve"><a href="use/resolve.html" >resolve</a></li>
+<li id="xooki-use/resources"><a href="use/resources.html" >resources</a></li>
+<li id="xooki-use/retrieve"><a href="use/retrieve.html" >retrieve</a></li>
+<li id="xooki-use/report" class="submenu"><a href="use/report.html"
>report</a><ul class="closed"><li id="xooki-yed"><a href="yed.html" >Using yEd
to layout report graphs</a></li>
+</ul></li>
+<li id="xooki-use/settings"><a href="use/settings.html" >settings</a></li>
+<li id="xooki-use/var"><a href="use/var.html" >var</a></li>
+</ul></li>
+<li id="xooki-standalone"><a href="standalone.html" >Using standalone</a></li>
+<li id="xooki-osgi" class="submenu"><a href="osgi.html" >OSGi</a><ul
class="closed"><li id="xooki-osgi/osgi-mapping"><a
href="osgi/osgi-mapping.html" >OSGi mapping</a></li>
+<li id="xooki-osgi/eclipse-plugin"><a href="osgi/eclipse-plugin.html"
>Building an Eclipse plugin</a></li>
+<li id="xooki-osgi/standard-osgi"><a href="osgi/standard-osgi.html" >Building
a standard OSGi bundle</a></li>
+<li id="xooki-osgi/target-platform"><a href="osgi/target-platform.html"
>Managing a target platform</a></li>
+<li id="xooki-osgi/sigil"><a href="osgi/sigil.html" >Apache Felix
Sigil</a></li>
+</ul></li>
+</ul></li>
+<li id="xooki-dev" class="submenu"><a href="dev.html" >Developer doc</a><ul
class="closed"><li id="xooki-extend"><a href="extend.html" >Extending
Ivy</a></li>
+<li id="xooki-dev/makerelease"><a href="dev/makerelease.html" >Making a
release</a></li>
+</ul></li>
+</ul></li>
+</ul>
+</div>
+
+ <center><iframe src="http://www.apache.org/ads/buttonbar.html";
+ style="border-width:0;" frameborder="0" scrolling="no"
+ width="135" height="265"></iframe>
+ </center>
+
+ </div>
+
+ </td>
+
+ <td valign="top">
+ <div id="main">
+
+ <h1 class="title">Documentation (trunk)</h1>
+ <br class="xooki-br"/> Ivy is sending http headers when
downloading files.<br class="xooki-br"/> The User-Agent http header can be
controlled using a <pre>http.agent</pre> system property.<br class="xooki-br"/>
When this system property is not set, the default value for the User-Agent
header is "Apache Ivy/ivyversion"<br class="xooki-br"/> where ivyversion is
replaced by the currently running version of ivy.<br class="xooki-br"/>
+ </div><!-- main -->
+ </td>
+ </tr>
+</table>
+
+<table id="footer-menu" summary="Navigation elements." border="0"
+ cellpadding="0" cellspacing="0" width="100%">
+ <tr>
+ <td align="center" valign="middle">
+ <div class="primary-links">::
+ <a href="index.html">Home</a> ::
+ <a href="download.html">Download</a> ::
+ <a
href="history/latest-milestone/index.html">Documentation</a> ::
+ <a href="get-involved.html">Get Involved</a> ::
+ <a href="search.html">Search</a> ::
+ </div>
+ </td>
+ </tr>
+</table>
+
+<div id="footer-message" class="footer">
+ <hr />
+ <i>Copyright © 2014 The Apache Software Foundation, Licensed under
the <a href="http://www.apache.org/licenses/LICENSE-2.0.txt";>Apache License,
Version 2.0</a>.</i><br />
+ <i>Apache Ivy, Apache Ant, Ivy, Ant, Apache, the Apache Ivy logo, the
Apache Ant logo and the Apache feather logo are trademarks of The Apache
Software Foundation.</i><br />
+ <i>All other marks mentioned may be trademarks or registered trademarks of
their respective owners. </i>
+</div>
+
+</div><!-- body -->
+</body>
+</html>
Propchange: ant/site/ivy/production/history/trunk/running.html
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: ant/site/ivy/production/history/trunk/running.html
------------------------------------------------------------------------------
svn:keywords = Date Revision Author HeadURL Id
Propchange: ant/site/ivy/production/history/trunk/running.html
------------------------------------------------------------------------------
svn:mime-type = text/html
Modified: ant/site/ivy/production/history/trunk/standalone.html
URL:
http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/standalone.html?rev=1590249&r1=1590248&r2=1590249&view=diff
==============================================================================
--- ant/site/ivy/production/history/trunk/standalone.html (original)
+++ ant/site/ivy/production/history/trunk/standalone.html Sat Apr 26 16:52:13
2014
@@ -237,7 +237,7 @@
<div id="main">
<h1 class="title">Using standalone</h1>
- <br class="xooki-br"/>Ivy can be used as a standalone program very
easily. All you need is a java 1.4+ runtime environment (JRE)!<br
class="xooki-br"/><br class="xooki-br"/>Then here is how to call it:
+ <br class="xooki-br"/>Ivy can be used as a standalone program very
easily. All you need is a Java 5+ runtime environment (JRE)!<br
class="xooki-br"/><br class="xooki-br"/>Then here is how to call it:
<pre>
java -jar ivy.jar -?
</pre>
