Repository: ant-ivy Updated Branches: refs/heads/master d2e4494b4 -> b126634a2
Documentation revision: refreshing/fixing links Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo Commit: http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/b126634a Tree: http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/b126634a Diff: http://git-wip-us.apache.org/repos/asf/ant-ivy/diff/b126634a Branch: refs/heads/master Commit: b126634a28243a06d65a73434877936718c60a06 Parents: d2e4494 Author: Gintas Grigelionis <[email protected]> Authored: Sun Sep 17 09:27:47 2017 +0200 Committer: Gintas Grigelionis <[email protected]> Committed: Sun Sep 17 10:26:18 2017 +0200 ---------------------------------------------------------------------- asciidoc/bestpractices.adoc | 2 +- asciidoc/concept.adoc | 4 ++-- asciidoc/dev.adoc | 4 ++-- asciidoc/dev/makerelease.adoc | 8 ++++---- asciidoc/index.adoc | 4 ++-- asciidoc/moreexamples.adoc | 2 +- asciidoc/osgi.adoc | 2 +- asciidoc/osgi/eclipse-plugin.adoc | 8 ++++---- asciidoc/osgi/sigil.adoc | 2 +- asciidoc/osgi/standard-osgi.adoc | 6 +++--- asciidoc/osgi/target-platform.adoc | 2 +- asciidoc/resolver/packager.adoc | 2 +- asciidoc/resolver/vfs.adoc | 2 +- asciidoc/settings/resolvers.adoc | 2 +- asciidoc/tutorial.adoc | 4 ++-- asciidoc/use/report.adoc | 2 +- asciidoc/use/resources.adoc | 2 +- asciidoc/use/retrieve.adoc | 2 +- asciidoc/yed.adoc | 4 ++-- 19 files changed, 32 insertions(+), 32 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/bestpractices.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/bestpractices.adoc b/asciidoc/bestpractices.adoc index babb828..3402252 100644 --- a/asciidoc/bestpractices.adoc +++ b/asciidoc/bestpractices.adoc @@ -49,7 +49,7 @@ A public repository usually contains much more than what you actually need. Is t === Security -The artifacts you download from a module repository are often executable, and are thus a security concern. Imagine a hacker replacing commons-lang by another version containing a virus? If you rely on a public repository to build your software, you expose it to a security risk. You can read more about that in this link:http://www.fortifysoftware.com/servlet/downloads/public/fortify_attacking_the_build.pdf[Forrester article]. +The artifacts you download from a module repository are often executable, and are thus a security concern. Imagine a hacker replacing commons-lang by another version containing a virus? If you rely on a public repository to build your software, you expose it to a security risk. You can read more about that in this link:https://www.helpnetsecurity.com/dl/articles/fortify_attacking_the_build.pdf[Forrester article]. Note that using an enterprise repository doesn't mean you have to build it entirely by hand. Ivy features an link:use/install.html[install] task which can be used to install modules from one repository to another one, so it can be used to selectively install modules from a public repository to your enterprise repository, where you will then be able to ensure control, reliability and accuracy. http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/concept.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/concept.adoc b/asciidoc/concept.adoc index 878aa46..2ce1b0b 100644 --- a/asciidoc/concept.adoc +++ b/asciidoc/concept.adoc @@ -346,9 +346,9 @@ A __packaged__ artifact needs to be declared as such in the module descriptor vi * `zip`, `jar` or `war`: the artifact will be uncompressed as a folder -* `pack200`: the artifact will be unpacked to a file via the link:http://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html[pack200] algorithm +* `pack200`: the artifact will be unpacked to a file via the link:https://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html[pack200] algorithm -* `bundle`: the OSGi artifact will be uncompressed as a folder, and every embedded jar file entry which is packed via the the link:http://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html[pack200] algorithm will be unpacked +* `bundle`: the OSGi artifact will be uncompressed as a folder, and every embedded jar file entry which is packed via the the link:https://docs.oracle.com/javase/7/docs/technotes/tools/share/pack200.html[pack200] algorithm will be unpacked So, if in an `ivy.xml`, there would be declared a such artifact: http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/dev.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/dev.adoc b/asciidoc/dev.adoc index f6302c9..645e9b7 100644 --- a/asciidoc/dev.adoc +++ b/asciidoc/dev.adoc @@ -28,7 +28,7 @@ All you need is * an link:https://git-scm.com/downloads[Git] client + _to check out Ivy sources from Apache Git, not required if you build from sources packaged in a release_ -* link:http://ant.apache.org/[Apache Ant] 1.9.0 or greater + +* link:https://ant.apache.org/[Apache Ant] 1.9.0 or greater + _We recommend the latest version of Ant_ * a link:http://www.oracle.com/technetwork/java/javase/downloads/index.html[JDK] 7 or greater + @@ -116,4 +116,4 @@ Download the file and unzip its content in your Eclipse installation directory. The Ivy project comes with settings for the link:http://eclipse-cs.sourceforge.net/[Checkstyle plugin] we recommend to use to avoid introducing a new digression to the Checkstyle rules we use. If you use this plugin, you will see many errors in Ivy. As we said, following strict Checkstyle rules is a work in progress and we used to have pretty different code conventions (like using _ as prefix for private attributes), so we still have things to fix. We usually use the filter in the problems view to filter out Checkstyle errors from this view, which helps to know what the real compilation problem are. -Besides this plugin we also recommend to use a subversion plugin, link:http://www.eclipse.org/subversive/[subversive] or link:http://subclipse.tigris.org[subclipse] being the two options currently available in the open source landscape. +Besides this plugin we also recommend to use a Git plugin, link:https://www.eclipse.org/egit/[EGit]. http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/dev/makerelease.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/dev/makerelease.adoc b/asciidoc/dev/makerelease.adoc index e44a075..4aa819b 100644 --- a/asciidoc/dev/makerelease.adoc +++ b/asciidoc/dev/makerelease.adoc @@ -100,7 +100,7 @@ Be prepared to enter your passphrase several times if you use this script, gpg w ==== 7. Prepare the Eclipse update site -To be able to test the release within IvyDE, it can be deployed in the IvyDE update site. See link:http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html[that page] to know how to process. +To be able to test the release within IvyDE, it can be deployed in the IvyDE update site. See link:https://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html[that page] to know how to process. ==== 8. Publish the release candidate @@ -187,7 +187,7 @@ If the release is approved, it's now time to make it public. The artifacts in th svn mv https://dist.apache.org/repos/dist/dev/ant/ivy/$VERSION https://dist.apache.org/repos/dist/release/ant/ivy/$VERSION ---- -In order to keep the main dist area of a reasonable size, old releases should be removed. They will disappear from the main dist but will still be available via the link:http://archive.apache.org/dist/ant/ivy/[archive]. To do so, just use the `svn rm` command against the artifacts or folders to remove. +In order to keep the main dist area of a reasonable size, old releases should be removed. They will disappear from the main dist but will still be available via the link:https://archive.apache.org/dist/ant/ivy/[archive]. To do so, just use the `svn rm` command against the artifacts or folders to remove. ==== 13. Promote the Maven staging repository @@ -197,7 +197,7 @@ Select the appropriate `orgapacheant-XXXX` repository and select the __Release__ ==== 14. Update the web site -It's time to update the download image used on the home page and the download page. Use site/images/ivy-dl.xcf as a basis if you have link:http://www.gimp.org/[gimp] installed. Then you can update the home page to refer to this image, and add a news item announcing the new version. Update also the download page with the new image and update the links to the download location (using a search/replace on the html source is recommended for this). +It's time to update the download image used on the home page and the download page. Use site/images/ivy-dl.xcf as a basis if you have link:https://www.gimp.org/[gimp] installed. Then you can update the home page to refer to this image, and add a news item announcing the new version. Update also the download page with the new image and update the links to the download location (using a search/replace on the html source is recommended for this). The just release documentation should be added to the site. To do so, you need to: @@ -245,7 +245,7 @@ svn add --force sources ==== 15. Deploy the Eclipse updatesite -If the Eclipse update site has already been prepared to include that new Ivy release, it is now needed to be deployed. Then follow the deployment instruction on link:http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html[that page]. +If the Eclipse update site has already been prepared to include that new Ivy release, it is now needed to be deployed. Then follow the deployment instruction on link:https://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html[that page]. ==== 16. Announce http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/index.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/index.adoc b/asciidoc/index.adoc index 60d14c5..b930408 100644 --- a/asciidoc/index.adoc +++ b/asciidoc/index.adoc @@ -27,7 +27,7 @@ Ivy is a tool for managing (recording, tracking, resolving and reporting) projec . tight integration with Apache Ant - while available as a standalone tool, Ivy works particularly well with Apache Ant providing a number of powerful Ant tasks ranging from dependency resolution to dependency reporting and publication. -Ivy is open source and released under a very permissive link:http://www.apache.org/licenses/[Apache License]. +Ivy is open source and released under a very permissive link:https://www.apache.org/licenses/[Apache License]. Ivy has a lot of powerful link:https://ant.apache.org/ivy/features.html[features], the most popular and useful being its flexibility, integration with Ant, and its strong transitive dependencies management engine. @@ -42,7 +42,7 @@ Tip: The menu on the left is dynamic, you can click on the arrows to browse the This documentation has been migrated from the old Ivy web site hosted by Jayasoft, feel free to report any problem on the link:https://ant.apache.org/ivy/mailing-lists.html[mailing-lists]. -If you browse this documentation from your installation of Ivy, you can also check the link:http://ant.apache.org/ivy/[online version] for the latest updates. +If you browse this documentation from your installation of Ivy, you can also check the link:https://ant.apache.org/ivy/[online version] for the latest updates. You can also browse this documentation offline either by downloading the documentation distribution, or by checking out the doc directory from git. This documentation uses link:http://asciidoctor.org/[asciidoc] as its documentation engine, so you can very easily link:https://ant.apache.org/ivy/get-involved.html[edit it and submit patches] when you browse it from source. http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/moreexamples.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/moreexamples.adoc b/asciidoc/moreexamples.adoc index e904c46..da797b8 100644 --- a/asciidoc/moreexamples.adoc +++ b/asciidoc/moreexamples.adoc @@ -34,7 +34,7 @@ The link:https://web.archive.org/web/20130613141751/https://java.net/projects/sp == Webwork -The link:https://web.archive.org/web/20101203144930/http://www.opensymphony.com/webwork/[Webwork project] (which became Struts Action framework) uses Ant+Ivy for their build, and thus makes their framework very easy to use in an Ant+Ivy build system. They have a link:http://wiki.opensymphony.com/display/WW/Dependencies[page documenting how to use Ivy with their framework], which can be an interesting reading, even if you don't plan to use Webwork. +The link:https://web.archive.org/web/20101203144930/http://www.opensymphony.com/webwork/[Webwork project] (which became Struts Action framework) uses Ant+Ivy for their build, and thus makes their framework very easy to use in an Ant+Ivy build system. They have a link:https://web.archive.org/web/20080807181009/http://wiki.opensymphony.com/display/WW/Dependencies[page documenting how to use Ivy with their framework], which can be an interesting reading, even if you don't plan to use Webwork. == Easing multi-module development http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/osgi.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/osgi.adoc b/asciidoc/osgi.adoc index 5609ea6..05261a1 100644 --- a/asciidoc/osgi.adoc +++ b/asciidoc/osgi.adoc @@ -23,7 +23,7 @@ Since Apache Ivy™ 2.3, some support for OSGi™ dependency management ha -WARNING: Note that this feature is considered as *experimental*. It should work with simple configuration but may not in complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:http://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:http://ant.apache.org/ivy/mailing-lists.html[ant-dev]. +WARNING: Note that this feature is considered as *experimental*. It should work with simple configuration but may not in complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:https://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:https://ant.apache.org/ivy/mailing-lists.html[ant-dev]. So with a standard ivy.xml, you can express some dependency on some OSGi bundle and every of their transitive dependencies will be resolved. You can also declare in your ivy.xml some OSGi dependency, like a `Require-Bundle`, an `Import-Package` or an `Import-Service`, miming an OSGi MANIFEST.MF. http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/osgi/eclipse-plugin.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/osgi/eclipse-plugin.adoc b/asciidoc/osgi/eclipse-plugin.adoc index 0d142f0..5c8f774 100644 --- a/asciidoc/osgi/eclipse-plugin.adoc +++ b/asciidoc/osgi/eclipse-plugin.adoc @@ -23,7 +23,7 @@ ==== Note that this feature is considered as *experimental*. -It should work with a simple configuration but may not with complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:http://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:http://ant.apache.org/ivy/mailing-lists.html[ant-dev]. +It should work with a simple configuration but may not with complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:https://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:https://ant.apache.org/ivy/mailing-lists.html[ant-dev]. ==== @@ -41,9 +41,9 @@ In a few steps, we will set up a build to compile and package an Eclipse plugin. * in the `ivy.xml`, change the symbolic name declared in the extends element - * *__(optional)__* by default the `build.xml` is expecting the sources to be in the `src` folder. You may want to edit it if it is not the case + * (*__optional__*) by default the `build.xml` is expecting the sources to be in the `src` folder. You may want to edit it if it is not the case - * *__(optional)__* if Ivy is not in Ant's classpath, link:http://ant.apache.org/ivy/download.cgi[download the Ivy jar] and edit the `build.xml` accordingly (see the comments at the beginning of the file) + * (*__optional__*) if Ivy is not in Ant's classpath, link:https://ant.apache.org/ivy/download.cgi[download the Ivy jar] and edit the `build.xml` accordingly (see the comments at the beginning of the file) And that's it ! Now let's use it. @@ -68,7 +68,7 @@ ant build === Eclipse setup -You probably have already configured your project in Eclipse via the PDE. Let's see how to change that and use link:http://ant.apache.org/ivy/ivyde/[Apache IvyDE]: +You probably have already configured your project in Eclipse via the PDE. Let's see how to change that and use link:https://ant.apache.org/ivy/ivyde/[Apache IvyDE]: * First remove from your project's classpath the PDE dependencies container http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/osgi/sigil.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/osgi/sigil.adoc b/asciidoc/osgi/sigil.adoc index 062000b..269e9a8 100644 --- a/asciidoc/osgi/sigil.adoc +++ b/asciidoc/osgi/sigil.adoc @@ -27,7 +27,7 @@ Another initiative to manage OSGi™ dependencies is the project link:https:/ Apache Felix Sigil is at its core about managing OSGi dependencies, not directly related to Ivy. Most of its core feature is about the implementation of the not yet released OBR (OSGi Bundle Repository) specification. It then provides integration layers with several tools so that developers can use the OBR API. It provides an Eclipse plugin and there are the Ant/Ivy tasks and resolvers. -On the other hand the built-in OSGi capabilities in Ivy are targeted towards users already familiar with Ivy and link:http://ant.apache.org/ivy/links.html[tools around it] like link:http://ant.apache.org/ivy/ivyde[Apache IvyDE™]. So with a minimum amount of effort, they can get OSGi dependency management. +On the other hand the built-in OSGi capabilities in Ivy are targeted towards users already familiar with Ivy and link:https://ant.apache.org/ivy/links.html[tools around it] like link:https://ant.apache.org/ivy/ivyde[Apache IvyDE™]. So with a minimum amount of effort, they can get OSGi dependency management. == Resulting differences http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/osgi/standard-osgi.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/osgi/standard-osgi.adoc b/asciidoc/osgi/standard-osgi.adoc index 2504830..dbe6ab0 100644 --- a/asciidoc/osgi/standard-osgi.adoc +++ b/asciidoc/osgi/standard-osgi.adoc @@ -23,7 +23,7 @@ ==== Note that this feature is considered as *experimental*. -It should work with simple configuration but may not in complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:http://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:http://ant.apache.org/ivy/mailing-lists.html[ant-dev]. +It should work with simple configuration but may not in complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:https://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:https://ant.apache.org/ivy/mailing-lists.html[ant-dev]. ==== @@ -49,9 +49,9 @@ In few steps, we will setup a build to compile and publish an OSGi bundle. * in the `ivysettings.properties`, specify the location of the plugins folder of your Eclipse target - * *__(optional)__* by default the `build.xml` is expecting the sources to be in the `src` folder. You may want to edit it if it is not the case + * (*__optional__*) by default the `build.xml` is expecting the sources to be in the `src` folder. You may want to edit it if it is not the case - * *__(optional)__* if Ivy is not in Ant's classpath, link:http://ant.apache.org/ivy/download.cgi[download the Ivy jar] and edit the `build.xml` accordingly (see the comments at the beginning of the file) + * (*__optional__*) if Ivy is not in Ant's classpath, link:https://ant.apache.org/ivy/download.cgi[download the Ivy jar] and edit the `build.xml` accordingly (see the comments at the beginning of the file) To build the project, run: http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/osgi/target-platform.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/osgi/target-platform.adoc b/asciidoc/osgi/target-platform.adoc index 11128aa..c8e7eb3 100644 --- a/asciidoc/osgi/target-platform.adoc +++ b/asciidoc/osgi/target-platform.adoc @@ -23,7 +23,7 @@ ==== Note that this feature is considered as *experimental*. -It should work with a simple configuration but may not with complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:http://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:http://ant.apache.org/ivy/mailing-lists.html[ant-dev]. +It should work with a simple configuration but may not with complex ones. If you have any issue with that feature, you are welcomed to come discuss your use case on the link:https://ant.apache.org/ivy/mailing-lists.html[ivy-user] mailing list, or discuss about implementation issues or improvement you may have found, on link:https://ant.apache.org/ivy/mailing-lists.html[ant-dev]. ==== http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/resolver/packager.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/resolver/packager.adoc b/asciidoc/resolver/packager.adoc index d4c2764..30b4ac6 100644 --- a/asciidoc/resolver/packager.adoc +++ b/asciidoc/resolver/packager.adoc @@ -268,7 +268,7 @@ The artifact children of m2resource tags support the following attributes: -Below is an example of packaging instructions for the link:http://commons.apache.org/email/[Apache Commons Email] module. Note that no build tag is required because all of the Maven 2 artifacts are usable directly (i.e., without unpacking anything). +Below is an example of packaging instructions for the link:https://commons.apache.org/proper/commons-email/[Apache Commons Email] module. Note that no build tag is required because all of the Maven 2 artifacts are usable directly (i.e., without unpacking anything). [source] ---- http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/resolver/vfs.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/resolver/vfs.adoc b/asciidoc/resolver/vfs.adoc index c320579..17a865d 100644 --- a/asciidoc/resolver/vfs.adoc +++ b/asciidoc/resolver/vfs.adoc @@ -28,7 +28,7 @@ [*__since 1.4__*] -This resolver is certainly the most capable, since it relies on link:http://jakarta.apache.org/commons/vfs/[Apache Commons VFS], which gives an uniform access to link:http://jakarta.apache.org/commons/vfs/filesystems.html[a good number of file systems], including FTP, WebDAV, zip, ... +This resolver is certainly the most capable, since it relies on link:https://commons.apache.org/proper/commons-vfs/[Apache Commons VFS], which gives an uniform access to link:https://commons.apache.org/proper/commons-vfs/filesystems.html[a good number of file systems], including FTP, WebDAV, zip, ... == Attributes http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/settings/resolvers.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/settings/resolvers.adoc b/asciidoc/settings/resolvers.adoc index a81bd58..f0fc915 100644 --- a/asciidoc/settings/resolvers.adoc +++ b/asciidoc/settings/resolvers.adoc @@ -66,7 +66,7 @@ Here is the list of built-in resolvers: |link:../resolver/packager.html[Packager]|Standard|Finds Ivy files and packaging instructions via URLs, then creates artifacts by following the instructions. |link:../resolver/filesystem.html[FileSystem]|Standard|This very performant resolver finds Ivy files and artifacts in your file system. |link:../resolver/url.html[URL]|Standard|Finds Ivy files and artifacts in any repository accessible with URLs. -|link:../resolver/vfs.html[VFS]|Standard|Finds Ivy files and artifacts in any repository accessible with link:http://jakarta.apache.org/commons/vfs/[Apache Commons VFS]. +|link:../resolver/vfs.html[VFS]|Standard|Finds Ivy files and artifacts in any repository accessible with link:https://commons.apache.org/proper/commons-vfs/[Apache Commons VFS]. |link:../resolver/ssh.html[SSH]|Standard|Finds Ivy files and artifacts in any repository accessible with SSH. |link:../resolver/sftp.html[SFTP]|Standard|Finds Ivy files and artifacts in any repository accessible with SFTP. |link:../resolver/jar.html[Jar]|Standard|Finds Ivy files and artifacts within a specified jar. http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/tutorial.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/tutorial.adoc b/asciidoc/tutorial.adoc index 94f9f29..5205105 100644 --- a/asciidoc/tutorial.adoc +++ b/asciidoc/tutorial.adoc @@ -26,13 +26,13 @@ For the first tutorial you won't even have to install Ivy (assuming you have Ant == First Tutorial - * Make sure you have link:http://ant.apache.org/[Ant] 1.9.9 or greater and a link:https://www.java.com/en/download/[Java JDK] properly installed + + * Make sure you have link:https://ant.apache.org/[Ant] 1.9.9 or greater and a link:http://www.oracle.com/technetwork/java/javase/downloads/index.html[Java JDK] properly installed + * Copy link:samples/build.xml[this build file] to an empty directory on your local filesystem (and make sure you name it `build.xml`) + * Open a console in that directory and run the command: `ant`. That's it! + -If you have any trouble, check our link:http://ant.apache.org/ivy/faq.html[FAQ]. +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.html[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). http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/use/report.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/use/report.adoc b/asciidoc/use/report.adoc index 9cf9561..541fcf8 100644 --- a/asciidoc/use/report.adoc +++ b/asciidoc/use/report.adoc @@ -23,7 +23,7 @@ This task should be used only after a call to resolve, even if the call was not In fact, this task uses XML report generated by resolve in cache. So if you call resolve on a module for a given configuration, you can call report safely on this module and this configuration as long as you do not clean your Ivy cache. If you want to have an idea of what reports look like, check this very simple link:../samples/jayasoft-ivyrep-example-default.html[example]. -The task also generates a GraphML file which can be loaded with the free link:http://www.yworks.com/en/products_yed_about.htm[yEd] graph editor. +The task also generates a GraphML file which can be loaded with the free link:https://www.yworks.com/products/yed[yEd] graph editor. Then following a few link:../yed.html[simple steps] you can obtain a graph like this link:../samples/jayasoft-ivyrep-example-default.jpg[one]. (*__since 1.4__*) If a custom XSLT is specified, it's possible to specify additional parameters to the stylesheet. http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/use/resources.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/use/resources.adoc b/asciidoc/use/resources.adoc index 9d285ee..28b088b 100644 --- a/asciidoc/use/resources.adoc +++ b/asciidoc/use/resources.adoc @@ -19,7 +19,7 @@ [*__since 2.3__*] (*__Ant 1.7 required__*) -`ivy:resources` is an Ant link:http://ant.apache.org/manual/Types/resources.html#collection[resource collection], containing files found by an Ivy resolve, which then can be used with any task working with resources like `copy` or `import`. +`ivy:resources` is an Ant link:https://ant.apache.org/manual/Types/resources.html#collection[resource collection], containing files found by an Ivy resolve, which then can be used with any task working with resources like `copy` or `import`. This datatype shares the same attributes, child elements and behaviour of a link:../use/postresolvetask.html[post resolve task]. It is not expected to be used as an Ant task though, only as a resource collection. http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/use/retrieve.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/use/retrieve.adoc b/asciidoc/use/retrieve.adoc index 05f11bb..0b752e0 100644 --- a/asciidoc/use/retrieve.adoc +++ b/asciidoc/use/retrieve.adoc @@ -28,7 +28,7 @@ The synchronisation actually consists in deleting all filles and directories in The root destination directory is the the directory denoted by the first level up the first token in the destination pattern. For instance, for the pattern `lib/[conf]/[artifact].[ext]`, the root will be `lib`. -(*__since 2.3__*) A nested link:http://ant.apache.org/manual/Types/mapper.html[mapper] element can be used to specify more complex filename transformations of the retrieved files. See the examples below. +(*__since 2.3__*) A nested link:https://ant.apache.org/manual/Types/mapper.html[mapper] element can be used to specify more complex filename transformations of the retrieved files. See the examples below. == Attributes http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/b126634a/asciidoc/yed.adoc ---------------------------------------------------------------------- diff --git a/asciidoc/yed.adoc b/asciidoc/yed.adoc index 9c1471b..3699082 100644 --- a/asciidoc/yed.adoc +++ b/asciidoc/yed.adoc @@ -17,7 +17,7 @@ under the License. //// -link:http://www.yworks.com/en/products_yed_about.htm[yEd] is a free graph editor, benefiting from all the automatic layouts of yFiles. Ivy is able to generate graphs which are readable by yEd. +link:https://www.yworks.com/products/yed[yEd] is a free graph editor, benefiting from all the automatic layouts of yFiles. Ivy is able to generate graphs which are readable by yEd. The graphs generated by Ivy are not laid out (in fact, it's why we use yEd), so you have to follow a simple sequence of steps to layout the generated graphs. @@ -52,4 +52,4 @@ That's all, you should have obtained something like this: image::images/yed-step7.jpg[] Note that this is only one possibility, test the available layouts yourself, you could find one better in your case. -Once you have laid out the graph, you can either save it with in the same file (but be warned that it will be overwritten at next Ivy report call), or another file, export it to JPEG, GIF, SVG, etc. (see link:http://www.yworks.com/en/products_yed_about.htm[yEd] site for details). +Once you have laid out the graph, you can either save it with in the same file (but be warned that it will be overwritten at next Ivy report call), or another file, export it to JPEG, GIF, SVG, etc. (see link:https://www.yworks.com/products/yed[yEd] site for details).
