ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jaiki...@apache.org
Subject svn commit: r1849619 [1/2] - in /ant/site/ivy/production: ./ history/2.4.0/ history/2.4.0/dev/ history/2.4.0/settings/ history/2.4.0/tutorial/ history/2.5.0-rc1/ history/2.5.0-rc1/dev/ history/2.5.0-rc1/settings/ history/2.5.0-rc1/tutorial/ history/lat...
Date Sun, 23 Dec 2018 13:28:58 GMT
Author: jaikiran
Date: Sun Dec 23 13:28:57 2018
New Revision: 1849619

URL: http://svn.apache.org/viewvc?rev=1849619&view=rev
Log:
Updates repository references to gitbox

Modified:
    ant/site/ivy/production/download.html
    ant/site/ivy/production/history/2.4.0/ant.html
    ant/site/ivy/production/history/2.4.0/book.html
    ant/site/ivy/production/history/2.4.0/dev/makerelease.html
    ant/site/ivy/production/history/2.4.0/extend.html
    ant/site/ivy/production/history/2.4.0/install.html
    ant/site/ivy/production/history/2.4.0/settings/outputters.html
    ant/site/ivy/production/history/2.4.0/tutorial.html
    ant/site/ivy/production/history/2.4.0/tutorial/build-repository.html
    ant/site/ivy/production/history/2.4.0/tutorial/multiproject.html
    ant/site/ivy/production/history/2.5.0-rc1/ant.html
    ant/site/ivy/production/history/2.5.0-rc1/book.html
    ant/site/ivy/production/history/2.5.0-rc1/dev/makerelease.html
    ant/site/ivy/production/history/2.5.0-rc1/extend.html
    ant/site/ivy/production/history/2.5.0-rc1/install.html
    ant/site/ivy/production/history/2.5.0-rc1/settings/outputters.html
    ant/site/ivy/production/history/2.5.0-rc1/tutorial.html
    ant/site/ivy/production/history/2.5.0-rc1/tutorial/build-repository.html
    ant/site/ivy/production/history/2.5.0-rc1/tutorial/multiproject.html
    ant/site/ivy/production/history/latest-milestone/ant.html
    ant/site/ivy/production/history/latest-milestone/book.html
    ant/site/ivy/production/history/latest-milestone/dev/makerelease.html
    ant/site/ivy/production/history/latest-milestone/extend.html
    ant/site/ivy/production/history/latest-milestone/install.html
    ant/site/ivy/production/history/latest-milestone/settings/outputters.html
    ant/site/ivy/production/history/latest-milestone/tutorial.html
    ant/site/ivy/production/history/latest-milestone/tutorial/build-repository.html
    ant/site/ivy/production/history/latest-milestone/tutorial/multiproject.html
    ant/site/ivy/production/history/master/ant.html
    ant/site/ivy/production/history/master/book.html
    ant/site/ivy/production/history/master/dev/makerelease.html
    ant/site/ivy/production/history/master/extend.html
    ant/site/ivy/production/history/master/install.html
    ant/site/ivy/production/history/master/settings/outputters.html
    ant/site/ivy/production/history/master/tutorial.html
    ant/site/ivy/production/history/master/tutorial/build-repository.html
    ant/site/ivy/production/history/master/tutorial/multiproject.html
    ant/site/ivy/production/write-doc.html

Modified: ant/site/ivy/production/download.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/download.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/download.html (original)
+++ ant/site/ivy/production/download.html Sun Dec 23 13:28:57 2018
@@ -185,7 +185,7 @@ To get information about the different k
 Older releases of Apache Ivy can be found <a href="http://archive.apache.org/dist/ant/ivy/">here</a>. We highly recommend to not use those releases but upgrade to the latest release.<br class="xooki-br"/><br class="xooki-br"/><h2>Building from source</h2>
 What you can get here at the ASF is the latest sources from the git repository:
 <pre>
-git clone <a href="https://git-wip-us.apache.org/repos/asf/ant-ivy.git">https://git-wip-us.apache.org/repos/asf/ant-ivy.git</a>
+git clone <a href="https://gitbox.apache.org/repos/asf/ant-ivy.git">https://gitbox.apache.org/repos/asf/ant-ivy.git</a>
 </pre>
 Then to build Apache Ivy from source, assuming you have Apache Ant&#153; 1.6.2+ and a jdk 1.5+ installed, then you only need to run the following command:
 <pre>

Modified: ant/site/ivy/production/history/2.4.0/ant.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/ant.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/ant.html (original)
+++ ant/site/ivy/production/history/2.4.0/ant.html Sun Dec 23 13:28:57 2018
@@ -247,7 +247,7 @@ Combined with the antlib definition in t
 <pre>
   &lt;taskdef name="ivy-configure" classname="org.apache.ivy.ant.IvyConfigure"/&gt;<br class="xooki-br"/>  &lt;taskdef name="ivy-resolve" classname="org.apache.ivy.ant.IvyResolve"/&gt;<br class="xooki-br"/>  &lt;taskdef name="ivy-retrieve" classname="org.apache.ivy.ant.IvyRetrieve"/&gt;<br class="xooki-br"/>  &lt;taskdef name="ivy-deliver" classname="org.apache.ivy.ant.IvyDeliver"/&gt; <br class="xooki-br"/>  &lt;taskdef name="ivy-publish" classname="org.apache.ivy.ant.IvyPublish"/&gt;
 </pre>
-<em>Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in git or the version you use.</em><br class="xooki-br"/><br class="xooki-br"/>Then you can use the tasks, but check their name, following samples assume you use the ivy namespace (ivy:xxx tasks), whereas with ant 1.5 you cannot use namespace, and should therefore use ivy-xxx tasks if you have followed the taskdefs above.<br class="xooki-br"/><br class="xooki-br"/>If you use an ant version lower than 1.5.1, you can not use the ivy tasks... you should then call ivy as any external program.<br class="xooki-br"/><h1>Calling ivy from ant: first steps</h1>
+<em>Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in git or the version you use.</em><br class="xooki-br"/><br class="xooki-br"/>Then you can use the tasks, but check their name, following samples assume you use the ivy namespace (ivy:xxx tasks), whereas with ant 1.5 you cannot use namespace, and should therefore use ivy-xxx tasks if you have followed the taskdefs above.<br class="xooki-br"/><br class="xooki-br"/>If you use an ant version lower than 1.5.1, you can not use the ivy tasks... you should then call ivy as any external program.<br class="xooki-br"/><h1>Calling ivy from ant: first steps</h1>
 Once your build file is ok to call ivy tasks, the simplest way to use ivy is to call the ivy retrieve task with no parameters:
 <pre>
 &lt;ivy:retrieve /&gt;
@@ -268,7 +268,7 @@ To understand more accurately the behavi
 <pre>
 ivy.project.dir = ${basedir}<br class="xooki-br"/>ivy.lib.dir = ${ivy.project.dir}/lib<br class="xooki-br"/>ivy.build.artifacts.dir = ${ivy.project.dir}/build/artifacts<br class="xooki-br"/>ivy.distrib.dir = ${ivy.project.dir}/distrib<br class="xooki-br"/>	<br class="xooki-br"/>ivy.resolver.default.check.modified = false<br class="xooki-br"/>ivy.default.always.check.exact.revision = true<br class="xooki-br"/><br class="xooki-br"/>ivy.configurations = *<br class="xooki-br"/>ivy.resolve.default.type.filter = *<br class="xooki-br"/>ivy.status = integration<br class="xooki-br"/>ivy.dep.file = ivy.xml<br class="xooki-br"/>ivy.settings.file = ivysettings.xml<br class="xooki-br"/>ivy.retrieve.pattern = ${ivy.lib.dir}/[artifact]-[revision].[ext]<br class="xooki-br"/>ivy.deliver.ivy.pattern = ${ivy.distrib.dir}/[type]s/[artifact]-[revision].[ext]<br class="xooki-br"/>ivy.publish.src.artifacts.pattern = ${ivy.distrib.dir}/[type]s/[artifact]-[revision].[ext]<br class="xooki-br"/><br class="xoo
 ki-br"/>ivy.report.output.pattern = [organisation]-[module]-[conf].[ext]<br class="xooki-br"/><br class="xooki-br"/>ivy.buildlist.ivyfilepath = ivy.xml<br class="xooki-br"/><br class="xooki-br"/>ivy.checksums=sha1,md5
 </pre>
-<em>For the latest version of these properties, you can check the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">git version</a>.</em><br class="xooki-br"/><br class="xooki-br"/><span class="since">since 2.0</span> After calling the first Ivy task, the property ivy.version will be available and contains the version of the used Ivy library. <br class="xooki-br"/><br class="xooki-br"/><h1>Ivy tasks attributes : generalities</h1>
+<em>For the latest version of these properties, you can check the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">git version</a>.</em><br class="xooki-br"/><br class="xooki-br"/><span class="since">since 2.0</span> After calling the first Ivy task, the property ivy.version will be available and contains the version of the used Ivy library. <br class="xooki-br"/><br class="xooki-br"/><h1>Ivy tasks attributes : generalities</h1>
 Some tasks attributes values may be given through different places. The three possible places are :<br class="xooki-br"/><ol>
 <li>task attribute</li>
 <li>ivy instance</li>

Modified: ant/site/ivy/production/history/2.4.0/book.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/book.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/book.html (original)
+++ ant/site/ivy/production/history/2.4.0/book.html Sun Dec 23 13:28:57 2018
@@ -222,7 +222,7 @@ Here is the list of people who have cont
 <li>Copy <a href="samples/build.xml">this build file</a> in an empty directory on your local filesystem (and make sure you name it build.xml)</li>
 <li>Open a console in this directory and run "ant". That's it!</li>
 </ol>
-If you have any trouble, check the <a href="http://ant.apache.org/ivy/faq.html">FAQ</a>. It is most likely related to your internet connection (proxy anyone?).<br class="xooki-br"/><br class="xooki-br"/>OK, you've just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <tt><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a></tt> directory).<br class="xooki-br"/><br class="xooki-br"/>The following tutorials are available:
+If you have any trouble, check the <a href="http://ant.apache.org/ivy/faq.html">FAQ</a>. It is most likely related to your internet connection (proxy anyone?).<br class="xooki-br"/><br class="xooki-br"/>OK, you've just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <tt><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a></tt> directory).<br class="xooki-br"/><br class="xooki-br"/>The following tutorials are available:
 <ul>
 <li><a href="tutorial/start.html">Quick Start</a></li> 
 Guides you through your very first steps with ivy.
@@ -581,11 +581,11 @@ For sure this is not aimed to demonstrat
 Modules in yellow are the modules described in this tutorial, and modules in blue are external dependencies (we will see how to generate this graph later in this tutorial).<br class="xooki-br"/><br class="xooki-br"/>As you can see, we have here a pretty interesting set of modules with dependencies between each other, each depending on the latest version of the others.<br class="xooki-br"/><br class="xooki-br"/><h1>The example files</h1>
 The sources for this tutorial can be found in <tt>src/example/multi-project</tt> in the Ivy distribution. In this directory, you will find the following files:
 <ul>
-<li><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a></li>This is a root build file which can be used to call targets on all modules, in the order of their dependencies (ensuring that a module is always built before any module depending on it, for instance)
+<li><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a></li>This is a root build file which can be used to call targets on all modules, in the order of their dependencies (ensuring that a module is always built before any module depending on it, for instance)
 <li>common
 <ul>
-<li><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a></li> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.
-<li><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a></li>some properties common to all projects
+<li><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a></li> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.
+<li><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a></li>some properties common to all projects
 </ul>
 </li>
 <li>projects</li>
@@ -702,7 +702,7 @@ The project that we will use is pretty s
 Z:\ivy-repository>ant -p<br class="xooki-br"/>Buildfile: build.xml<br class="xooki-br"/><br class="xooki-br"/>Main targets:<br class="xooki-br"/><br class="xooki-br"/> clean-cache            --> clean the cache<br class="xooki-br"/> clean-repo             --> clean the destination repository<br class="xooki-br"/> maven2                 --> install module from maven 2 repository<br class="xooki-br"/> maven2-deps            --> install module from maven 2 repository with dependencies<br class="xooki-br"/> maven2-namespace       --> install module from maven 2 using namespaces<br class="xooki-br"/> maven2-namespace-deps  --> install module with dependencies from maven2 repo using namespaces<br class="xooki-br"/>Default target: basic
 </pre></div>
 <br/><br/>
-This project is accessible in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a><br class="xooki-br"/><br class="xooki-br"/>Next steps:<br class="xooki-br"/><a href="tutorial/build-repository/basic.html">Basic repository copy</a><br class="xooki-br"/><a href="tutorial/build-repository/advanced.html">Using namespaces</a><br class="xooki-br"/><br class="xooki-br"/><br class="xooki-br"/>	<hr/><div class='toc-title toc-title-4'>Basic repository copy</div><br class="xooki-br"/>In this first step, we use the <a href="use/install.html">install</a> Ant task to install modules from the maven 2 repository to a file system based repository. We first install a module by itself, excluding dependencies, then again with its dependencies.<br class="xooki-br"/><br class="xooki-br"/><h1>Basic: ivysettings.xml file used</h1>
+This project is accessible in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a><br class="xooki-br"/><br class="xooki-br"/>Next steps:<br class="xooki-br"/><a href="tutorial/build-repository/basic.html">Basic repository copy</a><br class="xooki-br"/><a href="tutorial/build-repository/advanced.html">Using namespaces</a><br class="xooki-br"/><br class="xooki-br"/><br class="xooki-br"/>	<hr/><div class='toc-title toc-title-4'>Basic repository copy</div><br class="xooki-br"/>In this first step, we use the <a href="use/install.html">install</a> Ant task to install modules from the maven 2 repository to a file system based repository. We first install a module by itself, excluding dependencies, then again with its dependencies.<br class="xooki-br"/><br class="xooki-br"/><h1>Basic: ivysettings.xml file used</h1>
 The ivy settings file that we will use is very simple here. It defines two resolvers, <i>libraries</i> and <i>my-repository</i>. The first one is used as the source, the second one as the destination. In a typical setup, the second one would be configured using an <a href="settings/include.html">include</a> that included an existing settings file used by the development team.<br class="xooki-br"/>
 <pre>
 &lt;ivysettings&gt;<br class="xooki-br"/>	&lt;settings	defaultResolver="libraries"<br class="xooki-br"/>			defaultConflictManager="all" /&gt;		&lt;!-- in order to get all revisions without any eviction --&gt;<br class="xooki-br"/>	&lt;caches defaultCacheDir="${ivy.cache.dir}/no-namespace" /&gt;<br class="xooki-br"/>	&lt;resolvers&gt;<br class="xooki-br"/>		&lt;ibiblio name="libraries" m2compatible="true" /&gt;<br class="xooki-br"/>  		&lt;filesystem name="my-repository"&gt;<br class="xooki-br"/>  			&lt;ivy pattern="${dest.repo.dir}/no-namespace/[organisation]/[module]/ivys/ivy-[revision].xml"/&gt;<br class="xooki-br"/>  			&lt;artifact pattern="${dest.repo.dir}/no-namespace/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/&gt;<br class="xooki-br"/>  		&lt;/filesystem&gt;<br class="xooki-br"/>	&lt;/resolvers&gt;<br class="xooki-br"/>&lt;/ivysettings&gt;
@@ -1081,7 +1081,7 @@ If you want to use Ivy only in your ant
     &lt;property name="ivy.install.version" value="2.1.0-rc2" /&gt;<br class="xooki-br"/>    &lt;condition property="ivy.home" value="${env.IVY_HOME}"&gt;<br class="xooki-br"/>      &lt;isset property="env.IVY_HOME" /&gt;<br class="xooki-br"/>    &lt;/condition&gt;<br class="xooki-br"/>    &lt;property name="ivy.home" value="${user.home}/.ant" /&gt;<br class="xooki-br"/>    &lt;property name="ivy.jar.dir" value="${ivy.home}/lib" /&gt;<br class="xooki-br"/>    &lt;property name="ivy.jar.file" value="${ivy.jar.dir}/ivy.jar" /&gt;<br class="xooki-br"/><br class="xooki-br"/>    &lt;target name="download-ivy" unless="offline"&gt;<br class="xooki-br"/><br class="xooki-br"/>        &lt;mkdir dir="${ivy.jar.dir}"/&gt;<br class="xooki-br"/>        &lt;!-- download Ivy from web site so that it can be used even without any special installation --&gt;<br class="xooki-br"/>        &lt;get src="https://repo1.maven.org/maven2/org/apache/ivy/ivy/${ivy.install.version}/ivy-${ivy.install.version}.jar
 " <br class="xooki-br"/>             dest="${ivy.jar.file}" usetimestamp="true"/&gt;<br class="xooki-br"/>    &lt;/target&gt;<br class="xooki-br"/><br class="xooki-br"/>    &lt;target name="init-ivy" depends="download-ivy"&gt;<br class="xooki-br"/>      &lt;!-- try to load ivy here from ivy home, in case the user has not already dropped<br class="xooki-br"/>              it into ant's lib dir (note that the latter copy will always take precedence).<br class="xooki-br"/>              We will not fail as long as local lib dir exists (it may be empty) and<br class="xooki-br"/>              ivy is in at least one of ant's lib dir or the local lib dir. --&gt;<br class="xooki-br"/>        &lt;path id="ivy.lib.path"&gt;<br class="xooki-br"/>            &lt;fileset dir="${ivy.jar.dir}" includes="*.jar"/&gt;<br class="xooki-br"/><br class="xooki-br"/>        &lt;/path&gt;<br class="xooki-br"/>        &lt;taskdef resource="org/apache/ivy/ant/antlib.xml"<br class="xooki-br"/>                 u
 ri="antlib:org.apache.ivy.ant" classpathref="ivy.lib.path"/&gt;<br class="xooki-br"/>    &lt;/target&gt;
 </pre>
 
-Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.<br class="xooki-br"/>	<hr/><div class='toc-title toc-title-3'>Settings Files</div><br class="xooki-br"/>In order to work as you want, ivy sometimes needs some settings. Actually, ivy can work with no specific settings at all, see the <a href="tutorial/defaultconf.html">default settings documentation</a> for details about that. But ivy is able to work in very different contexts. You just have to configure it properly.<br class="xooki-br"/><br class="xooki-br"/>Settings are specified through an xml file, usually called ivysettings.xml. To configure ivy from ant, you just have to use the <a href="use/settings.html">settings</a> datatype with the path of your settings 
 file.<br class="xooki-br"/><br class="xooki-br"/>Here is an example of the settings file:
+Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.<br class="xooki-br"/>	<hr/><div class='toc-title toc-title-3'>Settings Files</div><br class="xooki-br"/>In order to work as you want, ivy sometimes needs some settings. Actually, ivy can work with no specific settings at all, see the <a href="tutorial/defaultconf.html">default settings documentation</a> for details about that. But ivy is able to work in very different contexts. You just have to configure it properly.<br class="xooki-br"/><br class="xooki-br"/>Settings are specified through an xml file, usually called ivysettings.xml. To configure ivy from ant, you just have to use the <a href="use/settings.html">settings</a> datatype with the path of your settings file
 .<br class="xooki-br"/><br class="xooki-br"/>Here is an example of the settings file:
 <pre>
 &lt;ivysettings&gt;<br class="xooki-br"/>        &lt;properties file="${ivy.settings.dir}/ivysettings-file.properties" /&gt;<br class="xooki-br"/>        &lt;settings defaultResolver="ibiblio" /&gt;<br class="xooki-br"/>        &lt;caches  defaultCacheDir="${cache.dir}" checkUpToDate="false" /&gt;<br class="xooki-br"/>        &lt;resolvers&gt;<br class="xooki-br"/>                &lt;ibiblio name="ibiblio" /&gt;<br class="xooki-br"/>                &lt;filesystem name="internal"&gt;<br class="xooki-br"/>                        &lt;ivy pattern="${repository.dir}/[module]/ivy-[revision].xml" /&gt;<br class="xooki-br"/>                        &lt;artifact pattern="${repository.dir}/[module]/[artifact]-[revision].[ext]" /&gt;<br class="xooki-br"/>                &lt;/filesystem&gt;<br class="xooki-br"/>        &lt;/resolvers&gt;<br class="xooki-br"/>        &lt;modules&gt;<br class="xooki-br"/>                &lt;module organisation="jayasoft" name=".*" resolver="internal" /&gt;<br clas
 s="xooki-br"/>        &lt;/modules&gt;<br class="xooki-br"/>&lt;/ivysettings&gt;
 </pre>
@@ -2856,11 +2856,11 @@ Uses 'fix-103' as default branch for all
 
 A report outputter is used at the end of the resolve process to generate a report of how the resolve has been performed.<br class="xooki-br"/><br class="xooki-br"/>Two report outputters are registered by default:
 <ul>
-<li>a log report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)</li>which produces the output on the console at the end of the resolve, which looks like this:
+<li>a log report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)</li>which produces the output on the console at the end of the resolve, which looks like this:
 <pre>
         ---------------------------------------------------------------------<br class="xooki-br"/>        |                  |            modules            ||   artifacts   |<br class="xooki-br"/>        |       conf       | number| search|dwnlded|evicted|| number|dwnlded|<br class="xooki-br"/>        ---------------------------------------------------------------------<br class="xooki-br"/>        |      default     |   1   |   1   |   0   |   0   ||   1   |   1   |<br class="xooki-br"/>        ---------------------------------------------------------------------
 </pre>
-<li>an xml report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)</li>which produces an xml report in the cache, which is mandatory for correct Ivy behaviour, since it's that report which is used when you do a post resolve step in a separate build from the resolve itself. It's also this xml report which is processed to generate all the different reports available in the <a href="use/report.html">report</a> task.
+<li>an xml report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)</li>which produces an xml report in the cache, which is mandatory for correct Ivy behaviour, since it's that report which is used when you do a post resolve step in a separate build from the resolve itself. It's also this xml report which is processed to generate all the different reports available in the <a href="use/report.html">report</a> task.
 </ul>
 
 The child tag used for the parser must be equal to a name of a report outputter type (added with the typedef tag).<br class="xooki-br"/><br class="xooki-br"/>To see how to define your own report outputter see <a href="../extend.html">Extending Ivy documentation</a><br class="xooki-br"/><br class="xooki-br"/><h1>Child elements</h1>
@@ -4055,7 +4055,7 @@ Combined with the antlib definition in t
 <pre>
   &lt;taskdef name="ivy-configure" classname="org.apache.ivy.ant.IvyConfigure"/&gt;<br class="xooki-br"/>  &lt;taskdef name="ivy-resolve" classname="org.apache.ivy.ant.IvyResolve"/&gt;<br class="xooki-br"/>  &lt;taskdef name="ivy-retrieve" classname="org.apache.ivy.ant.IvyRetrieve"/&gt;<br class="xooki-br"/>  &lt;taskdef name="ivy-deliver" classname="org.apache.ivy.ant.IvyDeliver"/&gt; <br class="xooki-br"/>  &lt;taskdef name="ivy-publish" classname="org.apache.ivy.ant.IvyPublish"/&gt;
 </pre>
-<em>Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in git or the version you use.</em><br class="xooki-br"/><br class="xooki-br"/>Then you can use the tasks, but check their name, following samples assume you use the ivy namespace (ivy:xxx tasks), whereas with ant 1.5 you cannot use namespace, and should therefore use ivy-xxx tasks if you have followed the taskdefs above.<br class="xooki-br"/><br class="xooki-br"/>If you use an ant version lower than 1.5.1, you can not use the ivy tasks... you should then call ivy as any external program.<br class="xooki-br"/><h1>Calling ivy from ant: first steps</h1>
+<em>Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in git or the version you use.</em><br class="xooki-br"/><br class="xooki-br"/>Then you can use the tasks, but check their name, following samples assume you use the ivy namespace (ivy:xxx tasks), whereas with ant 1.5 you cannot use namespace, and should therefore use ivy-xxx tasks if you have followed the taskdefs above.<br class="xooki-br"/><br class="xooki-br"/>If you use an ant version lower than 1.5.1, you can not use the ivy tasks... you should then call ivy as any external program.<br class="xooki-br"/><h1>Calling ivy from ant: first steps</h1>
 Once your build file is ok to call ivy tasks, the simplest way to use ivy is to call the ivy retrieve task with no parameters:
 <pre>
 &lt;ivy:retrieve /&gt;
@@ -4076,7 +4076,7 @@ To understand more accurately the behavi
 <pre>
 ivy.project.dir = ${basedir}<br class="xooki-br"/>ivy.lib.dir = ${ivy.project.dir}/lib<br class="xooki-br"/>ivy.build.artifacts.dir = ${ivy.project.dir}/build/artifacts<br class="xooki-br"/>ivy.distrib.dir = ${ivy.project.dir}/distrib<br class="xooki-br"/>	<br class="xooki-br"/>ivy.resolver.default.check.modified = false<br class="xooki-br"/>ivy.default.always.check.exact.revision = true<br class="xooki-br"/><br class="xooki-br"/>ivy.configurations = *<br class="xooki-br"/>ivy.resolve.default.type.filter = *<br class="xooki-br"/>ivy.status = integration<br class="xooki-br"/>ivy.dep.file = ivy.xml<br class="xooki-br"/>ivy.settings.file = ivysettings.xml<br class="xooki-br"/>ivy.retrieve.pattern = ${ivy.lib.dir}/[artifact]-[revision].[ext]<br class="xooki-br"/>ivy.deliver.ivy.pattern = ${ivy.distrib.dir}/[type]s/[artifact]-[revision].[ext]<br class="xooki-br"/>ivy.publish.src.artifacts.pattern = ${ivy.distrib.dir}/[type]s/[artifact]-[revision].[ext]<br class="xooki-br"/><br class="xoo
 ki-br"/>ivy.report.output.pattern = [organisation]-[module]-[conf].[ext]<br class="xooki-br"/><br class="xooki-br"/>ivy.buildlist.ivyfilepath = ivy.xml<br class="xooki-br"/><br class="xooki-br"/>ivy.checksums=sha1,md5
 </pre>
-<em>For the latest version of these properties, you can check the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">git version</a>.</em><br class="xooki-br"/><br class="xooki-br"/><span class="since">since 2.0</span> After calling the first Ivy task, the property ivy.version will be available and contains the version of the used Ivy library. <br class="xooki-br"/><br class="xooki-br"/><h1>Ivy tasks attributes : generalities</h1>
+<em>For the latest version of these properties, you can check the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">git version</a>.</em><br class="xooki-br"/><br class="xooki-br"/><span class="since">since 2.0</span> After calling the first Ivy task, the property ivy.version will be available and contains the version of the used Ivy library. <br class="xooki-br"/><br class="xooki-br"/><h1>Ivy tasks attributes : generalities</h1>
 Some tasks attributes values may be given through different places. The three possible places are :<br class="xooki-br"/><ol>
 <li>task attribute</li>
 <li>ivy instance</li>
@@ -5897,7 +5897,7 @@ The Ivy project comes with settings for
 <li>triggers</li>
 </ul>
 
-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://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/java/org/apache/ivy/plugins">org.apache.ivy.plugins</a> package. In each package you will find a
 n 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>
+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://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/java/org/apache/ivy/plugins">org.apache.ivy.plugins</a> package. In each package you will find an in
 terface 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 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>
@@ -5949,7 +5949,7 @@ git push --tags
 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>9. Call for a vote to approve the release</h3>
 Cast a vote to approve the release on the dev@ant.apache.org 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"/>The svn tag of this release is: <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-OF-THE-TAG">https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-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
+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://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-OF-THE-TAG">https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-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>10. Publish the release</h3>
 

Modified: ant/site/ivy/production/history/2.4.0/dev/makerelease.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/dev/makerelease.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/dev/makerelease.html (original)
+++ ant/site/ivy/production/history/2.4.0/dev/makerelease.html Sun Dec 23 13:28:57 2018
@@ -291,7 +291,7 @@ git push --tags
 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>9. Call for a vote to approve the release</h3>
 Cast a vote to approve the release on the dev@ant.apache.org 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"/>The svn tag of this release is: <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-OF-THE-TAG">https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-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
+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://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-OF-THE-TAG">https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=SHA1-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>10. Publish the release</h3>
 

Modified: ant/site/ivy/production/history/2.4.0/extend.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/extend.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/extend.html (original)
+++ ant/site/ivy/production/history/2.4.0/extend.html Sun Dec 23 13:28:57 2018
@@ -252,7 +252,7 @@
 <li>triggers</li>
 </ul>
 
-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://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/java/org/apache/ivy/plugins">org.apache.ivy.plugins</a> package. In each package you will find a
 n 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"/>	
+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://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/java/org/apache/ivy/plugins">org.apache.ivy.plugins</a> package. In each package you will find an in
 terface 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"/>	
  		</div><!-- main -->
 		</td>
 	</tr>

Modified: ant/site/ivy/production/history/2.4.0/install.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/install.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/install.html (original)
+++ ant/site/ivy/production/history/2.4.0/install.html Sun Dec 23 13:28:57 2018
@@ -252,7 +252,7 @@ If you want to use Ivy only in your ant
     &lt;property name="ivy.install.version" value="2.1.0-rc2" /&gt;<br class="xooki-br"/>    &lt;condition property="ivy.home" value="${env.IVY_HOME}"&gt;<br class="xooki-br"/>      &lt;isset property="env.IVY_HOME" /&gt;<br class="xooki-br"/>    &lt;/condition&gt;<br class="xooki-br"/>    &lt;property name="ivy.home" value="${user.home}/.ant" /&gt;<br class="xooki-br"/>    &lt;property name="ivy.jar.dir" value="${ivy.home}/lib" /&gt;<br class="xooki-br"/>    &lt;property name="ivy.jar.file" value="${ivy.jar.dir}/ivy.jar" /&gt;<br class="xooki-br"/><br class="xooki-br"/>    &lt;target name="download-ivy" unless="offline"&gt;<br class="xooki-br"/><br class="xooki-br"/>        &lt;mkdir dir="${ivy.jar.dir}"/&gt;<br class="xooki-br"/>        &lt;!-- download Ivy from web site so that it can be used even without any special installation --&gt;<br class="xooki-br"/>        &lt;get src="https://repo1.maven.org/maven2/org/apache/ivy/ivy/${ivy.install.version}/ivy-${ivy.install.version}.jar
 " <br class="xooki-br"/>             dest="${ivy.jar.file}" usetimestamp="true"/&gt;<br class="xooki-br"/>    &lt;/target&gt;<br class="xooki-br"/><br class="xooki-br"/>    &lt;target name="init-ivy" depends="download-ivy"&gt;<br class="xooki-br"/>      &lt;!-- try to load ivy here from ivy home, in case the user has not already dropped<br class="xooki-br"/>              it into ant's lib dir (note that the latter copy will always take precedence).<br class="xooki-br"/>              We will not fail as long as local lib dir exists (it may be empty) and<br class="xooki-br"/>              ivy is in at least one of ant's lib dir or the local lib dir. --&gt;<br class="xooki-br"/>        &lt;path id="ivy.lib.path"&gt;<br class="xooki-br"/>            &lt;fileset dir="${ivy.jar.dir}" includes="*.jar"/&gt;<br class="xooki-br"/><br class="xooki-br"/>        &lt;/path&gt;<br class="xooki-br"/>        &lt;taskdef resource="org/apache/ivy/ant/antlib.xml"<br class="xooki-br"/>                 u
 ri="antlib:org.apache.ivy.ant" classpathref="ivy.lib.path"/&gt;<br class="xooki-br"/>    &lt;/target&gt;
 </pre>
 
-Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.<br class="xooki-br"/>	
+Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.<br class="xooki-br"/>	
  		</div><!-- main -->
 		</td>
 	</tr>

Modified: ant/site/ivy/production/history/2.4.0/settings/outputters.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/settings/outputters.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/settings/outputters.html (original)
+++ ant/site/ivy/production/history/2.4.0/settings/outputters.html Sun Dec 23 13:28:57 2018
@@ -242,11 +242,11 @@
 
 A report outputter is used at the end of the resolve process to generate a report of how the resolve has been performed.<br class="xooki-br"/><br class="xooki-br"/>Two report outputters are registered by default:
 <ul>
-<li>a log report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)</li>which produces the output on the console at the end of the resolve, which looks like this:
+<li>a log report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)</li>which produces the output on the console at the end of the resolve, which looks like this:
 <pre>
         ---------------------------------------------------------------------<br class="xooki-br"/>        |                  |            modules            ||   artifacts   |<br class="xooki-br"/>        |       conf       | number| search|dwnlded|evicted|| number|dwnlded|<br class="xooki-br"/>        ---------------------------------------------------------------------<br class="xooki-br"/>        |      default     |   1   |   1   |   0   |   0   ||   1   |   1   |<br class="xooki-br"/>        ---------------------------------------------------------------------
 </pre>
-<li>an xml report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)</li>which produces an xml report in the cache, which is mandatory for correct Ivy behaviour, since it's that report which is used when you do a post resolve step in a separate build from the resolve itself. It's also this xml report which is processed to generate all the different reports available in the <a href="../use/report.html">report</a> task.
+<li>an xml report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)</li>which produces an xml report in the cache, which is mandatory for correct Ivy behaviour, since it's that report which is used when you do a post resolve step in a separate build from the resolve itself. It's also this xml report which is processed to generate all the different reports available in the <a href="../use/report.html">report</a> task.
 </ul>
 
 The child tag used for the parser must be equal to a name of a report outputter type (added with the typedef tag).<br class="xooki-br"/><br class="xooki-br"/>To see how to define your own report outputter see <a href="../extend.html">Extending Ivy documentation</a><br class="xooki-br"/><br class="xooki-br"/><h1>Child elements</h1>

Modified: ant/site/ivy/production/history/2.4.0/tutorial.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/tutorial.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/tutorial.html (original)
+++ ant/site/ivy/production/history/2.4.0/tutorial.html Sun Dec 23 13:28:57 2018
@@ -244,7 +244,7 @@
 <li>Copy <a href="samples/build.xml">this build file</a> in an empty directory on your local filesystem (and make sure you name it build.xml)</li>
 <li>Open a console in this directory and run "ant". That's it!</li>
 </ol>
-If you have any trouble, check the <a href="http://ant.apache.org/ivy/faq.html">FAQ</a>. It is most likely related to your internet connection (proxy anyone?).<br class="xooki-br"/><br class="xooki-br"/>OK, you've just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <tt><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a></tt> directory).<br class="xooki-br"/><br class="xooki-br"/>The following tutorials are available:
+If you have any trouble, check the <a href="http://ant.apache.org/ivy/faq.html">FAQ</a>. It is most likely related to your internet connection (proxy anyone?).<br class="xooki-br"/><br class="xooki-br"/>OK, you've just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <tt><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a></tt> directory).<br class="xooki-br"/><br class="xooki-br"/>The following tutorials are available:
 <ul>
 <li><a href="tutorial/start.html">Quick Start</a></li> 
 Guides you through your very first steps with ivy.

Modified: ant/site/ivy/production/history/2.4.0/tutorial/build-repository.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/tutorial/build-repository.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/tutorial/build-repository.html (original)
+++ ant/site/ivy/production/history/2.4.0/tutorial/build-repository.html Sun Dec 23 13:28:57 2018
@@ -245,7 +245,7 @@ The project that we will use is pretty s
 Z:\ivy-repository>ant -p<br class="xooki-br"/>Buildfile: build.xml<br class="xooki-br"/><br class="xooki-br"/>Main targets:<br class="xooki-br"/><br class="xooki-br"/> clean-cache            --> clean the cache<br class="xooki-br"/> clean-repo             --> clean the destination repository<br class="xooki-br"/> maven2                 --> install module from maven 2 repository<br class="xooki-br"/> maven2-deps            --> install module from maven 2 repository with dependencies<br class="xooki-br"/> maven2-namespace       --> install module from maven 2 using namespaces<br class="xooki-br"/> maven2-namespace-deps  --> install module with dependencies from maven2 repo using namespaces<br class="xooki-br"/>Default target: basic
 </pre></div>
 <br/><br/>
-This project is accessible in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a><br class="xooki-br"/><br class="xooki-br"/>Next steps:<br class="xooki-br"/><a href="../tutorial/build-repository/basic.html">Basic repository copy</a><br class="xooki-br"/><a href="../tutorial/build-repository/advanced.html">Using namespaces</a><br class="xooki-br"/><br class="xooki-br"/><br class="xooki-br"/>	
+This project is accessible in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a><br class="xooki-br"/><br class="xooki-br"/>Next steps:<br class="xooki-br"/><a href="../tutorial/build-repository/basic.html">Basic repository copy</a><br class="xooki-br"/><a href="../tutorial/build-repository/advanced.html">Using namespaces</a><br class="xooki-br"/><br class="xooki-br"/><br class="xooki-br"/>	
  		</div><!-- main -->
 		</td>
 	</tr>

Modified: ant/site/ivy/production/history/2.4.0/tutorial/multiproject.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.4.0/tutorial/multiproject.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.4.0/tutorial/multiproject.html (original)
+++ ant/site/ivy/production/history/2.4.0/tutorial/multiproject.html Sun Dec 23 13:28:57 2018
@@ -254,11 +254,11 @@ For sure this is not aimed to demonstrat
 Modules in yellow are the modules described in this tutorial, and modules in blue are external dependencies (we will see how to generate this graph later in this tutorial).<br class="xooki-br"/><br class="xooki-br"/>As you can see, we have here a pretty interesting set of modules with dependencies between each other, each depending on the latest version of the others.<br class="xooki-br"/><br class="xooki-br"/><h1>The example files</h1>
 The sources for this tutorial can be found in <tt>src/example/multi-project</tt> in the Ivy distribution. In this directory, you will find the following files:
 <ul>
-<li><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a></li>This is a root build file which can be used to call targets on all modules, in the order of their dependencies (ensuring that a module is always built before any module depending on it, for instance)
+<li><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a></li>This is a root build file which can be used to call targets on all modules, in the order of their dependencies (ensuring that a module is always built before any module depending on it, for instance)
 <li>common
 <ul>
-<li><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a></li> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.
-<li><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a></li>some properties common to all projects
+<li><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a></li> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.
+<li><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a></li>some properties common to all projects
 </ul>
 </li>
 <li>projects</li>

Modified: ant/site/ivy/production/history/2.5.0-rc1/ant.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/ant.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/ant.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/ant.html Sun Dec 23 13:28:57 2018
@@ -243,7 +243,7 @@ hljs.initHighlightingOnLoad();</script><
 </div>
 </div>
 <div class="paragraph">
-<p><em>Note</em>: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in Git repository or the jar file you use.</p>
+<p><em>Note</em>: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in Git repository or the jar file you use.</p>
 </div>
 <div class="paragraph">
 <p>Then you can use the tasks, but check their name, following samples assume you use the Ivy namespace (ivy:xxx tasks), whereas with Ant 1.5 you cannot use namespace, and should therefore use ivy-xxx tasks if you have added the taskdefs as above.</p>
@@ -322,7 +322,7 @@ ivy.checksums=sha1,md5</code></pre>
 </div>
 </div>
 <div class="paragraph">
-<p><em>For the latest version of these properties, you can check the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">Git version</a>.</em></p>
+<p><em>For the latest version of these properties, you can check the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">Git version</a>.</em></p>
 </div>
 <div class="paragraph">
 <p>(<strong><em>since 2.0</em></strong>) After calling the first Ivy task, the property <code>ivy.version</code> will be available and contains the version of the used Ivy library.</p>

Modified: ant/site/ivy/production/history/2.5.0-rc1/book.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/book.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/book.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/book.html Sun Dec 23 13:28:57 2018
@@ -1220,7 +1220,7 @@ configurability, and tight integration w
 <p>If you have any trouble, check our <a href="https://ant.apache.org/ivy/faq.html">FAQ</a>.</p>
 </div>
 <div class="paragraph">
-<p>OK, you&#8217;ve just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a> directory).</p>
+<p>OK, you&#8217;ve just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a> directory).</p>
 </div>
 </div>
 </div>
@@ -2499,7 +2499,7 @@ give access to all other modules feature
 <div class="ulist">
 <ul>
 <li>
-<p><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a><br/>
+<p><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a><br/>
 This is a root build file which can be used to call targets on all modules, in the order of their dependencies (ensuring that a module is always built before any module depending on it, for instance)</p>
 </li>
 <li>
@@ -2507,10 +2507,10 @@ This is a root build file which can be u
 <div class="ulist">
 <ul>
 <li>
-<p><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.</p>
+<p><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.</p>
 </li>
 <li>
-<p><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a> some properties common to all projects</p>
+<p><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a> some properties common to all projects</p>
 </li>
 </ul>
 </div>
@@ -3036,7 +3036,7 @@ Default target: basic</code></pre>
 </div>
 </div>
 <div class="paragraph">
-<p>This project is accessible in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a></p>
+<p>This project is accessible in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a></p>
 </div>
 <div class="paragraph">
 <p>Next steps:<br/>
@@ -4849,7 +4849,7 @@ You can now run the build, if it is succ
 </div>
 </div>
 <div class="paragraph">
-<p>Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.</p>
+<p>Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.</p>
 </div>
 </div>
 </div>
@@ -10425,7 +10425,7 @@ You can greatly improve the performance
 <div class="ulist">
 <ul>
 <li>
-<p>a log report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)<br/>
+<p>a log report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)<br/>
 which produces the output on the console at the end of the resolve, which looks like this:</p>
 </li>
 </ul>
@@ -10443,7 +10443,7 @@ which produces the output on the console
 <div class="ulist">
 <ul>
 <li>
-<p>an xml report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)<br/>
+<p>an xml report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)<br/>
 which produces an XML report in the cache, which is mandatory for correct Ivy behaviour, since it&#8217;s that report which is used when you do a post resolve step in a separate build from the resolve itself. It&#8217;s also this XML report which is processed to generate all the different reports available in the <a href="../use/report.html">report</a> task.</p>
 </li>
 </ul>
@@ -14482,7 +14482,7 @@ specifying a fixed revision list, in whi
 </div>
 </div>
 <div class="paragraph">
-<p><em>Note</em>: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in Git repository or the jar file you use.</p>
+<p><em>Note</em>: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in Git repository or the jar file you use.</p>
 </div>
 <div class="paragraph">
 <p>Then you can use the tasks, but check their name, following samples assume you use the Ivy namespace (ivy:xxx tasks), whereas with Ant 1.5 you cannot use namespace, and should therefore use ivy-xxx tasks if you have added the taskdefs as above.</p>
@@ -14563,7 +14563,7 @@ ivy.checksums=sha1,md5</code></pre>
 </div>
 </div>
 <div class="paragraph">
-<p><em>For the latest version of these properties, you can check the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">Git version</a>.</em></p>
+<p><em>For the latest version of these properties, you can check the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">Git version</a>.</em></p>
 </div>
 <div class="paragraph">
 <p>(<strong><em>since 2.0</em></strong>) After calling the first Ivy task, the property <code>ivy.version</code> will be available and contains the version of the used Ivy library.</p>
@@ -20290,7 +20290,7 @@ If you use this plugin, you will see man
 <p>All Ivy plug-ins use the same code patterns as Ant specific tasks for parameters. This means that if you want to have a <code>myattribute</code> of type <code>String</code>, you just have to declare a method called <code>setMyattribute(String val)</code> on your plug-in. The same applies to child tags, you just have to follow Ant specifications.</p>
 </div>
 <div class="paragraph">
-<p>All pluggable code in Ivy is located in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=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.</p>
+<p>All pluggable code in Ivy is located in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=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.</p>
 </div>
 <div class="paragraph">
 <p>To understand how your implementation can be done, we suggest looking at existing implementations we provide, it&#8217;s the best way to get started.</p>
@@ -20505,7 +20505,7 @@ Use the right version number for the tag
 
 I have built a release candidate for Ivy ${version}
 
-The svn tag of this release is: https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version}
+The svn tag of this release is: https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version}
 
 The artifacts has been published to: https://dist.apache.org/repos/dist/dev/ant/ivy/${version} at revision ${svn-rev-of-the-check-in}
 

Modified: ant/site/ivy/production/history/2.5.0-rc1/dev/makerelease.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/dev/makerelease.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/dev/makerelease.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/dev/makerelease.html Sun Dec 23 13:28:57 2018
@@ -411,7 +411,7 @@ Use the right version number for the tag
 
 I have built a release candidate for Ivy ${version}
 
-The svn tag of this release is: https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version}
+The svn tag of this release is: https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version}
 
 The artifacts has been published to: https://dist.apache.org/repos/dist/dev/ant/ivy/${version} at revision ${svn-rev-of-the-check-in}
 

Modified: ant/site/ivy/production/history/2.5.0-rc1/extend.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/extend.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/extend.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/extend.html Sun Dec 23 13:28:57 2018
@@ -256,7 +256,7 @@ hljs.initHighlightingOnLoad();</script><
 <p>All Ivy plug-ins use the same code patterns as Ant specific tasks for parameters. This means that if you want to have a <code>myattribute</code> of type <code>String</code>, you just have to declare a method called <code>setMyattribute(String val)</code> on your plug-in. The same applies to child tags, you just have to follow Ant specifications.</p>
 </div>
 <div class="paragraph">
-<p>All pluggable code in Ivy is located in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=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.</p>
+<p>All pluggable code in Ivy is located in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=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.</p>
 </div>
 <div class="paragraph">
 <p>To understand how your implementation can be done, we suggest looking at existing implementations we provide, it&#8217;s the best way to get started.</p>

Modified: ant/site/ivy/production/history/2.5.0-rc1/install.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/install.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/install.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/install.html Sun Dec 23 13:28:57 2018
@@ -302,7 +302,7 @@ You can now run the build, if it is succ
 </div>
 </div>
 <div class="paragraph">
-<p>Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.</p>
+<p>Then the only thing to do is to add the init-ivy target in the depends attribute of your targets using Ivy, and add the ivy namespace to your build script. See the self contained <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml">go-ivy</a> example for details about this.</p>
 </div>
 </div>
 </div></div></div></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="reference.html">Reference</a>::<a href="tutorial.html">Tutorials</a>::<a href="dev.html">Developer's doc</a>::</div></td></tr></table><div id="footer-message" class="footer"><hr /><i>Copyright &copy; 2007 - 2018 The Apache Software Foundation, Licensed under the<a href="http://www.apache.org/licenses/">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></html>
\ No newline at end of file

Modified: ant/site/ivy/production/history/2.5.0-rc1/settings/outputters.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/settings/outputters.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/settings/outputters.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/settings/outputters.html Sun Dec 23 13:28:57 2018
@@ -226,7 +226,7 @@ hljs.initHighlightingOnLoad();</script><
 <div class="ulist">
 <ul>
 <li>
-<p>a log report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)<br/>
+<p>a log report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java">LogReportOutputter</a>)<br/>
 which produces the output on the console at the end of the resolve, which looks like this:</p>
 </li>
 </ul>
@@ -244,7 +244,7 @@ which produces the output on the console
 <div class="ulist">
 <ul>
 <li>
-<p>an xml report outputter (<a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)<br/>
+<p>an xml report outputter (<a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java">XmlReportOutputter</a>)<br/>
 which produces an XML report in the cache, which is mandatory for correct Ivy behaviour, since it&#8217;s that report which is used when you do a post resolve step in a separate build from the resolve itself. It&#8217;s also this XML report which is processed to generate all the different reports available in the <a href="../use/report.html">report</a> task.</p>
 </li>
 </ul>

Modified: ant/site/ivy/production/history/2.5.0-rc1/tutorial.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/tutorial.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/tutorial.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/tutorial.html Sun Dec 23 13:28:57 2018
@@ -239,7 +239,7 @@ hljs.initHighlightingOnLoad();</script><
 <p>If you have any trouble, check our <a href="https://ant.apache.org/ivy/faq.html">FAQ</a>.</p>
 </div>
 <div class="paragraph">
-<p>OK, you&#8217;ve just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a> directory).</p>
+<p>OK, you&#8217;ve just seen how easy it is to take your first step with Ivy. Go ahead with the other tutorials, but before you do, make sure you have properly <a href="install.html">installed</a> Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example">src/example</a> directory).</p>
 </div>
 </div>
 </div>

Modified: ant/site/ivy/production/history/2.5.0-rc1/tutorial/build-repository.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/tutorial/build-repository.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/tutorial/build-repository.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/tutorial/build-repository.html Sun Dec 23 13:28:57 2018
@@ -244,7 +244,7 @@ Default target: basic</code></pre>
 </div>
 </div>
 <div class="paragraph">
-<p>This project is accessible in the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a></p>
+<p>This project is accessible in the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example/build-a-ivy-repository">src/example/build-a-ivy-repository</a></p>
 </div>
 <div class="paragraph">
 <p>Next steps:<br/>

Modified: ant/site/ivy/production/history/2.5.0-rc1/tutorial/multiproject.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/2.5.0-rc1/tutorial/multiproject.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/2.5.0-rc1/tutorial/multiproject.html (original)
+++ ant/site/ivy/production/history/2.5.0-rc1/tutorial/multiproject.html Sun Dec 23 13:28:57 2018
@@ -283,7 +283,7 @@ give access to all other modules feature
 <div class="ulist">
 <ul>
 <li>
-<p><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a><br/>
+<p><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml">build.xml</a><br/>
 This is a root build file which can be used to call targets on all modules, in the order of their dependencies (ensuring that a module is always built before any module depending on it, for instance)</p>
 </li>
 <li>
@@ -291,10 +291,10 @@ This is a root build file which can be u
 <div class="ulist">
 <ul>
 <li>
-<p><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.</p>
+<p><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml">common.xml</a> the common build file imported by all build.xml files for each project. This build defines the targets which can be used in all projects.</p>
 </li>
 <li>
-<p><a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a> some properties common to all projects</p>
+<p><a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties">build.properties</a> some properties common to all projects</p>
 </li>
 </ul>
 </div>

Modified: ant/site/ivy/production/history/latest-milestone/ant.html
URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/ant.html?rev=1849619&r1=1849618&r2=1849619&view=diff
==============================================================================
--- ant/site/ivy/production/history/latest-milestone/ant.html (original)
+++ ant/site/ivy/production/history/latest-milestone/ant.html Sun Dec 23 13:28:57 2018
@@ -243,7 +243,7 @@ hljs.initHighlightingOnLoad();</script><
 </div>
 </div>
 <div class="paragraph">
-<p><em>Note</em>: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in Git repository or the jar file you use.</p>
+<p><em>Note</em>: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml">antlib.xml</a> file in Git repository or the jar file you use.</p>
 </div>
 <div class="paragraph">
 <p>Then you can use the tasks, but check their name, following samples assume you use the Ivy namespace (ivy:xxx tasks), whereas with Ant 1.5 you cannot use namespace, and should therefore use ivy-xxx tasks if you have added the taskdefs as above.</p>
@@ -322,7 +322,7 @@ ivy.checksums=sha1,md5</code></pre>
 </div>
 </div>
 <div class="paragraph">
-<p><em>For the latest version of these properties, you can check the <a href="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">Git version</a>.</em></p>
+<p><em>For the latest version of these properties, you can check the <a href="https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties">Git version</a>.</em></p>
 </div>
 <div class="paragraph">
 <p>(<strong><em>since 2.0</em></strong>) After calling the first Ivy task, the property <code>ivy.version</code> will be available and contains the version of the used Ivy library.</p>



Mime
View raw message