From notifications-return-32432-archive-asf-public=cust-asf.ponee.io@ant.apache.org Sun Dec 23 14:29:02 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 63873180677 for ; Sun, 23 Dec 2018 14:29:00 +0100 (CET) Received: (qmail 14597 invoked by uid 500); 23 Dec 2018 13:28:59 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 14481 invoked by uid 99); 23 Dec 2018 13:28:59 -0000 Received: from Unknown (HELO svn01-us-west.apache.org) (209.188.14.144) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Dec 2018 13:28:59 +0000 Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id D31443A1C38 for ; Sun, 23 Dec 2018 13:28:58 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1849619 [2/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 -0000 To: notifications@ant.apache.org From: jaikiran@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20181223132858.D31443A1C38@svn01-us-west.apache.org> Modified: ant/site/ivy/production/history/latest-milestone/book.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/book.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/book.html (original) +++ ant/site/ivy/production/history/latest-milestone/book.html Sun Dec 23 13:28:57 2018 @@ -1220,7 +1220,7 @@ configurability, and tight integration w

If you have any trouble, check our FAQ.

-

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

+

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

@@ -2499,7 +2499,7 @@ give access to all other modules feature
  • -

    build.xml
    +

    build.xml
    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)

  • @@ -2507,10 +2507,10 @@ This is a root build file which can be u
    • -

      common.xml 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.

      +

      common.xml 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.

    • -

      build.properties some properties common to all projects

      +

      build.properties some properties common to all projects

    @@ -3036,7 +3036,7 @@ Default target: basic
-

This project is accessible in the src/example/build-a-ivy-repository

+

This project is accessible in the src/example/build-a-ivy-repository

Next steps:
@@ -4849,7 +4849,7 @@ You can now run the build, if it is succ

-

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 go-ivy example for details about this.

+

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 go-ivy example for details about this.

@@ -10425,7 +10425,7 @@ You can greatly improve the performance
  • -

    a log report outputter (LogReportOutputter)
    +

    a log report outputter (LogReportOutputter)
    which produces the output on the console at the end of the resolve, which looks like this:

@@ -10443,7 +10443,7 @@ which produces the output on the console
  • -

    an xml report outputter (XmlReportOutputter)
    +

    an xml report outputter (XmlReportOutputter)
    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 report task.

@@ -14482,7 +14482,7 @@ specifying a fixed revision list, in whi
-

Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the antlib.xml file in Git repository or the jar file you use.

+

Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the antlib.xml file in Git repository or the jar file you use.

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.

@@ -14563,7 +14563,7 @@ ivy.checksums=sha1,md5
-

For the latest version of these properties, you can check the Git version.

+

For the latest version of these properties, you can check the Git version.

(since 2.0) After calling the first Ivy task, the property ivy.version will be available and contains the version of the used Ivy library.

@@ -20290,7 +20290,7 @@ If you use this plugin, you will see man

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.

-

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

+

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

To understand how your implementation can be done, we suggest looking at existing implementations we provide, it’s the best way to get started.

@@ -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/latest-milestone/dev/makerelease.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/dev/makerelease.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/dev/makerelease.html (original) +++ ant/site/ivy/production/history/latest-milestone/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/latest-milestone/extend.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/extend.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/extend.html (original) +++ ant/site/ivy/production/history/latest-milestone/extend.html Sun Dec 23 13:28:57 2018 @@ -256,7 +256,7 @@ hljs.initHighlightingOnLoad();<

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.

-

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

+

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

To understand how your implementation can be done, we suggest looking at existing implementations we provide, it’s the best way to get started.

Modified: ant/site/ivy/production/history/latest-milestone/install.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/install.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/install.html (original) +++ ant/site/ivy/production/history/latest-milestone/install.html Sun Dec 23 13:28:57 2018 @@ -302,7 +302,7 @@ You can now run the build, if it is succ
-

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 go-ivy example for details about this.

+

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 go-ivy example for details about this.

\ No newline at end of file Modified: ant/site/ivy/production/history/latest-milestone/settings/outputters.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/settings/outputters.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/settings/outputters.html (original) +++ ant/site/ivy/production/history/latest-milestone/settings/outputters.html Sun Dec 23 13:28:57 2018 @@ -226,7 +226,7 @@ hljs.initHighlightingOnLoad();<
  • -

    a log report outputter (LogReportOutputter)
    +

    a log report outputter (LogReportOutputter)
    which produces the output on the console at the end of the resolve, which looks like this:

@@ -244,7 +244,7 @@ which produces the output on the console
  • -

    an xml report outputter (XmlReportOutputter)
    +

    an xml report outputter (XmlReportOutputter)
    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 report task.

Modified: ant/site/ivy/production/history/latest-milestone/tutorial.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/tutorial.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/tutorial.html (original) +++ ant/site/ivy/production/history/latest-milestone/tutorial.html Sun Dec 23 13:28:57 2018 @@ -239,7 +239,7 @@ hljs.initHighlightingOnLoad();<

If you have any trouble, check our FAQ.

-

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

+

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

Modified: ant/site/ivy/production/history/latest-milestone/tutorial/build-repository.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/tutorial/build-repository.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/tutorial/build-repository.html (original) +++ ant/site/ivy/production/history/latest-milestone/tutorial/build-repository.html Sun Dec 23 13:28:57 2018 @@ -244,7 +244,7 @@ Default target: basic
-

This project is accessible in the src/example/build-a-ivy-repository

+

This project is accessible in the src/example/build-a-ivy-repository

Next steps:
Modified: ant/site/ivy/production/history/latest-milestone/tutorial/multiproject.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/latest-milestone/tutorial/multiproject.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/latest-milestone/tutorial/multiproject.html (original) +++ ant/site/ivy/production/history/latest-milestone/tutorial/multiproject.html Sun Dec 23 13:28:57 2018 @@ -283,7 +283,7 @@ give access to all other modules feature

  • -

    build.xml
    +

    build.xml
    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)

  • @@ -291,10 +291,10 @@ This is a root build file which can be u
    • -

      common.xml 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.

      +

      common.xml 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.

    • -

      build.properties some properties common to all projects

      +

      build.properties some properties common to all projects

    Modified: ant/site/ivy/production/history/master/ant.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/ant.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/ant.html (original) +++ ant/site/ivy/production/history/master/ant.html Sun Dec 23 13:28:57 2018 @@ -243,7 +243,7 @@ hljs.initHighlightingOnLoad();<
-

Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the antlib.xml file in Git repository or the jar file you use.

+

Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the antlib.xml file in Git repository or the jar file you use.

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.

@@ -322,7 +322,7 @@ ivy.checksums=sha1,md5
-

For the latest version of these properties, you can check the Git version.

+

For the latest version of these properties, you can check the Git version.

(since 2.0) After calling the first Ivy task, the property ivy.version will be available and contains the version of the used Ivy library.

Modified: ant/site/ivy/production/history/master/book.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/book.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/book.html (original) +++ ant/site/ivy/production/history/master/book.html Sun Dec 23 13:28:57 2018 @@ -1220,7 +1220,7 @@ configurability, and tight integration w

If you have any trouble, check our FAQ.

-

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

+

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

@@ -2499,7 +2499,7 @@ give access to all other modules feature
  • -

    build.xml
    +

    build.xml
    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)

  • @@ -2507,10 +2507,10 @@ This is a root build file which can be u
    • -

      common.xml 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.

      +

      common.xml 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.

    • -

      build.properties some properties common to all projects

      +

      build.properties some properties common to all projects

    @@ -3036,7 +3036,7 @@ Default target: basic
-

This project is accessible in the src/example/build-a-ivy-repository

+

This project is accessible in the src/example/build-a-ivy-repository

Next steps:
@@ -4849,7 +4849,7 @@ You can now run the build, if it is succ

-

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 go-ivy example for details about this.

+

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 go-ivy example for details about this.

@@ -10425,7 +10425,7 @@ You can greatly improve the performance
  • -

    a log report outputter (LogReportOutputter)
    +

    a log report outputter (LogReportOutputter)
    which produces the output on the console at the end of the resolve, which looks like this:

@@ -10443,7 +10443,7 @@ which produces the output on the console
  • -

    an xml report outputter (XmlReportOutputter)
    +

    an xml report outputter (XmlReportOutputter)
    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 report task.

@@ -14482,7 +14482,7 @@ specifying a fixed revision list, in whi
-

Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the antlib.xml file in Git repository or the jar file you use.

+

Note: the tasks listed above are non exhaustive. For a complete list of tasks with the corresponding classes, see the antlib.xml file in Git repository or the jar file you use.

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.

@@ -14563,7 +14563,7 @@ ivy.checksums=sha1,md5
-

For the latest version of these properties, you can check the Git version.

+

For the latest version of these properties, you can check the Git version.

(since 2.0) After calling the first Ivy task, the property ivy.version will be available and contains the version of the used Ivy library.

@@ -20290,7 +20290,7 @@ If you use this plugin, you will see man

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.

-

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

+

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

To understand how your implementation can be done, we suggest looking at existing implementations we provide, it’s the best way to get started.

@@ -20505,7 +20505,7 @@ Use the right version number for the tag I have built a release candidate for Ivy ${version} -The git tag of this release is: https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version} with the sha1 ${githash-of-tag} +The git tag of this release is: https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version} with the sha1 ${githash-of-tag} 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/master/dev/makerelease.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/dev/makerelease.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/dev/makerelease.html (original) +++ ant/site/ivy/production/history/master/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 git tag of this release is: https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version} with the sha1 ${githash-of-tag} +The git tag of this release is: https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/${version} with the sha1 ${githash-of-tag} 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/master/extend.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/extend.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/extend.html (original) +++ ant/site/ivy/production/history/master/extend.html Sun Dec 23 13:28:57 2018 @@ -256,7 +256,7 @@ hljs.initHighlightingOnLoad();<

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.

-

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

+

All pluggable code in Ivy is located in the org.apache.ivy.plugins 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.

To understand how your implementation can be done, we suggest looking at existing implementations we provide, it’s the best way to get started.

Modified: ant/site/ivy/production/history/master/install.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/install.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/install.html (original) +++ ant/site/ivy/production/history/master/install.html Sun Dec 23 13:28:57 2018 @@ -302,7 +302,7 @@ You can now run the build, if it is succ
-

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 go-ivy example for details about this.

+

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 go-ivy example for details about this.

\ No newline at end of file Modified: ant/site/ivy/production/history/master/settings/outputters.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/settings/outputters.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/settings/outputters.html (original) +++ ant/site/ivy/production/history/master/settings/outputters.html Sun Dec 23 13:28:57 2018 @@ -226,7 +226,7 @@ hljs.initHighlightingOnLoad();<
  • -

    a log report outputter (LogReportOutputter)
    +

    a log report outputter (LogReportOutputter)
    which produces the output on the console at the end of the resolve, which looks like this:

@@ -244,7 +244,7 @@ which produces the output on the console
  • -

    an xml report outputter (XmlReportOutputter)
    +

    an xml report outputter (XmlReportOutputter)
    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 report task.

Modified: ant/site/ivy/production/history/master/tutorial.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/tutorial.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/tutorial.html (original) +++ ant/site/ivy/production/history/master/tutorial.html Sun Dec 23 13:28:57 2018 @@ -239,7 +239,7 @@ hljs.initHighlightingOnLoad();<

If you have any trouble, check our FAQ.

-

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

+

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 installed Ivy and downloaded the tutorials sources (included in all Ivy distributions, in the src/example directory).

Modified: ant/site/ivy/production/history/master/tutorial/build-repository.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/tutorial/build-repository.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/tutorial/build-repository.html (original) +++ ant/site/ivy/production/history/master/tutorial/build-repository.html Sun Dec 23 13:28:57 2018 @@ -244,7 +244,7 @@ Default target: basic
-

This project is accessible in the src/example/build-a-ivy-repository

+

This project is accessible in the src/example/build-a-ivy-repository

Next steps:
Modified: ant/site/ivy/production/history/master/tutorial/multiproject.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/master/tutorial/multiproject.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/history/master/tutorial/multiproject.html (original) +++ ant/site/ivy/production/history/master/tutorial/multiproject.html Sun Dec 23 13:28:57 2018 @@ -283,7 +283,7 @@ give access to all other modules feature

  • -

    build.xml
    +

    build.xml
    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)

  • @@ -291,10 +291,10 @@ This is a root build file which can be u
    • -

      common.xml 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.

      +

      common.xml 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.

    • -

      build.properties some properties common to all projects

      +

      build.properties some properties common to all projects

    Modified: ant/site/ivy/production/write-doc.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/write-doc.html?rev=1849619&r1=1849618&r2=1849619&view=diff ============================================================================== --- ant/site/ivy/production/write-doc.html (original) +++ ant/site/ivy/production/write-doc.html Sun Dec 23 13:28:57 2018 @@ -162,7 +162,7 @@

    Contribute documentation


    Writing documentation for Apache Ivy™ is pretty simple.

    The documentation engine used is called xooki, and allows to edit pages while you browse them as soon as you browse them offline (and thus can actually save your modifications).

    To browse the doc offline, we recommend to check it out from git: 
    -git clone https://git-wip-us.apache.org/repos/asf/ant-ivy.git
+git clone https://gitbox.apache.org/repos/asf/ant-ivy.git
    Alternatively you can also check out the whole site: