This is an automated email from the ASF dual-hosted git repository.

bodewig pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ant-ivy.git


The following commit(s) were added to refs/heads/master by this push:
     new 7024863  moved to gitbox
7024863 is described below

commit 70248634fcdc141ceae8b5a5abcb266ce7230378
Author: Stefan Bodewig <[email protected]>
AuthorDate: Mon Dec 17 09:35:16 2018 +0100

    moved to gitbox
---
 asciidoc/ant.adoc                       | 4 ++--
 asciidoc/dev/makerelease.adoc           | 2 +-
 asciidoc/extend.adoc                    | 2 +-
 asciidoc/install.adoc                   | 2 +-
 asciidoc/settings/outputters.adoc       | 4 ++--
 asciidoc/tutorial.adoc                  | 2 +-
 asciidoc/tutorial/build-repository.adoc | 2 +-
 asciidoc/tutorial/multiproject.adoc     | 6 +++---
 doap_Ivy.rdf                            | 4 ++--
 9 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/asciidoc/ant.adoc b/asciidoc/ant.adoc
index ea42b14..bc04904 100644
--- a/asciidoc/ant.adoc
+++ b/asciidoc/ant.adoc
@@ -45,7 +45,7 @@ If you use Ant *1.5.1* or superior, you have to define the 
tasks you use in your
   <taskdef name="ivy-publish" classname="org.apache.ivy.ant.IvyPublish"/>
 ----
 
-_Note_: the tasks listed above are non exhaustive. For a complete list of 
tasks with the corresponding classes, see the 
link: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]
 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 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/ant/antlib.xml[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.
 
@@ -107,7 +107,7 @@ ivy.buildlist.ivyfilepath = ivy.xml
 ivy.checksums=sha1,md5
 ----
 
-_For the latest version of these properties, you can check the 
link: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]._
+_For the latest version of these properties, you can check the 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/core/settings/ivy.properties[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.
 
diff --git a/asciidoc/dev/makerelease.adoc b/asciidoc/dev/makerelease.adoc
index c641200..e320382 100644
--- a/asciidoc/dev/makerelease.adoc
+++ b/asciidoc/dev/makerelease.adoc
@@ -164,7 +164,7 @@ Subject: [VOTE] Ivy ${version} Release
 
 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}
 
diff --git a/asciidoc/extend.adoc b/asciidoc/extend.adoc
index 0077ebf..dadbcda 100644
--- a/asciidoc/extend.adoc
+++ b/asciidoc/extend.adoc
@@ -37,6 +37,6 @@ If you still don't find what you need, then you'll have to 
develop your own plug
 
 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 
link: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]
 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 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/java/org/apache/ivy/plugins[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.
diff --git a/asciidoc/install.adoc b/asciidoc/install.adoc
index 001f37a..eb1452f 100644
--- a/asciidoc/install.adoc
+++ b/asciidoc/install.adoc
@@ -85,4 +85,4 @@ If you want to use Ivy only in your Ant build scripts, and 
have an internet conn
 </project>
 ----
 
-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 
link:https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml[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 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/go-ivy/build.xml[go-ivy]
 example for details about this.
diff --git a/asciidoc/settings/outputters.adoc 
b/asciidoc/settings/outputters.adoc
index a41cb11..74eff7c 100644
--- a/asciidoc/settings/outputters.adoc
+++ b/asciidoc/settings/outputters.adoc
@@ -28,7 +28,7 @@ A report outputter is used at the end of the resolve process 
to generate a repor
 Two report outputters are registered by default:
 
 
-    * a log report outputter 
(link: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 log report outputter 
(link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/LogReportOutputter.java[LogReportOutputter])
 +
     which produces the output on the console at the end of the resolve, which 
looks like this:
 
 [source,shell]
@@ -44,7 +44,7 @@ Two report outputters are registered by default:
 ----
 
 
-    * an xml report outputter 
(link: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])
 +
+    * an xml report outputter 
(link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/java/org/apache/ivy/plugins/report/XmlReportOutputter.java[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 
link:../use/report{outfilesuffix}[report] task.
 
 
diff --git a/asciidoc/tutorial.adoc b/asciidoc/tutorial.adoc
index f1047e2..e026995 100644
--- a/asciidoc/tutorial.adoc
+++ b/asciidoc/tutorial.adoc
@@ -34,7 +34,7 @@ For the first tutorial you won't even have to install Ivy 
(assuming you have Ant
 
 If you have any trouble, check our 
link:https://ant.apache.org/ivy/faq.html[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 
link:install{outfilesuffix}[installed] Ivy and downloaded the tutorials sources 
(included in all Ivy distributions, in the 
link:https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example[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 
link:install{outfilesuffix}[installed] Ivy and downloaded the tutorials sources 
(included in all Ivy distributions, in the 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=tree;f=src/example[src/example]
 directory).
 
 == List of available tutorials
 
diff --git a/asciidoc/tutorial/build-repository.adoc 
b/asciidoc/tutorial/build-repository.adoc
index a86ce12..a25f929 100644
--- a/asciidoc/tutorial/build-repository.adoc
+++ b/asciidoc/tutorial/build-repository.adoc
@@ -52,7 +52,7 @@ Default target: basic
 
 
 
-This project is accessible in the 
link: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]
+This project is accessible in the 
link: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]
 
 Next steps: +
 link:../tutorial/build-repository/basic.html[Basic repository copy] +
diff --git a/asciidoc/tutorial/multiproject.adoc 
b/asciidoc/tutorial/multiproject.adoc
index 1f6fefb..27919b5 100644
--- a/asciidoc/tutorial/multiproject.adoc
+++ b/asciidoc/tutorial/multiproject.adoc
@@ -65,13 +65,13 @@ As you can see, we have here a pretty interesting set of 
modules with dependenci
 The sources for this tutorial can be found in `src/example/multi-project` in 
the Ivy distribution. In this directory, you will find the following files:
 
 
-* 
link:https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/build.xml[build.xml]
 +
+* 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/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)
 
 * common
 
-  ** 
link:https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml[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.
-  ** 
link:https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties[build.properties]
 some properties common to all projects
+  ** 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/common.xml[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.
+  ** 
link:https://gitbox.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=src/example/multi-project/common/build.properties[build.properties]
 some properties common to all projects
 
 +
 
diff --git a/doap_Ivy.rdf b/doap_Ivy.rdf
index 1db78dc..959c278 100644
--- a/doap_Ivy.rdf
+++ b/doap_Ivy.rdf
@@ -71,8 +71,8 @@
     </release>
     <repository>
       <GitRepository>
-        <location 
rdf:resource="https://git-wip-us.apache.org/repos/asf/ant-ivy.git"/>
-        <browse 
rdf:resource="https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git"/>
+        <location 
rdf:resource="https://gitbox.apache.org/repos/asf/ant-ivy.git"/>
+        <browse 
rdf:resource="https://gitbox.apache.org/repos/asf?p=ant-ivy.git"/>
       </GitRepository>
     </repository>
   </Project>

Reply via email to