Repository: ant-ivy Updated Branches: refs/heads/master d5281ad38 -> e124901cb
document and fix the release notes for IVY-1529 This closes #6 Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo Commit: http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/e124901c Tree: http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/e124901c Diff: http://git-wip-us.apache.org/repos/asf/ant-ivy/diff/e124901c Branch: refs/heads/master Commit: e124901cbd5afbc500eda9cd531eacbeade9d9ba Parents: d5281ad Author: Nicolas LaleveÌe <[email protected]> Authored: Sun May 21 19:59:24 2017 +0200 Committer: Nicolas LaleveÌe <[email protected]> Committed: Sun May 21 19:59:24 2017 +0200 ---------------------------------------------------------------------- doc/release-notes.html | 2 +- doc/settings/resolvers.html | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/e124901c/doc/release-notes.html ---------------------------------------------------------------------- diff --git a/doc/release-notes.html b/doc/release-notes.html index 4ddd75b..6093670 100644 --- a/doc/release-notes.html +++ b/doc/release-notes.html @@ -77,7 +77,7 @@ List of changes since Ivy 2.4.0: - IMPROVEMENT: Update bouncycastle to 1.52 (IVY-1521) (Thanks to Michal Srb) - NEW: Lets ssh-based resolvers use an ~/.ssh/config file to find username/hostname/keyfile options (Thanks to Colin Stanfill) -- NEW: Add ivy.maven.sources.lookup and ivy.maven.javadoc.lookup variables to control the lookup of the additional artifacts. Defaults to true, for backward compatibility (IVY-1529) +- NEW: Add ivy.maven.lookup.sources and ivy.maven.lookup.javadoc variables to control the lookup of the additional artifacts. Defaults to true, for backward compatibility (IVY-1529) - NEW: Add (conditional) support for SHA-256 SHA-512 and SHA-384 checksum algorithms (IVY-1554) (Thanks to Jaikiran Pai) <!-- Samples : http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/e124901c/doc/settings/resolvers.html ---------------------------------------------------------------------- diff --git a/doc/settings/resolvers.html b/doc/settings/resolvers.html index 1cb2018..13e4b6c 100644 --- a/doc/settings/resolvers.html +++ b/doc/settings/resolvers.html @@ -95,6 +95,13 @@ Any standard resolver can be used in force mode, which is used mainly to handle By using such a resolver at the beginning of a chain, you can be sure that Ivy will pick up whatever module is available in this resolver (usually a private local build) instead of the real requested revision. This allows to handle use case like a developer working on modules A and C, where A -> B -> C, and pick up the local build for C without having to publish a local version of B. <span class="since">since 2.0</span> +<h3>Maven</h3> + +Any resolver which is able to parse a Maven pom.xml file has to detect the related sources or javadocs artifacts. This often involves sevrals network connection even if neither the sources nor the javadoc are requested to be downloaded. + +<span class="since">since 2.5</span> Setting the property <tt>ivy.maven.lookup.sources<tt> to <tt>false</tt> disable the lookup of the sources artifact. +And setting the property <tt>ivy.maven.lookup.javadoc<tt> to <tt>false</tt> disable the lookup of the javadoc artifact. + <h2>Attributes</h2> <table class="ivy-attributes"> <thead>
