Modified: ant/ivy/site/target/history/trunk/configuration/resolvers.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/trunk/configuration/resolvers.html?rev=675851&r1=675850&r2=675851&view=diff ============================================================================== --- ant/ivy/site/target/history/trunk/configuration/resolvers.html (original) +++ ant/ivy/site/target/history/trunk/configuration/resolvers.html Fri Jul 11 00:44:05 2008 @@ -132,8 +132,13 @@ </tbody> </table> -<h1><a name="common">Common attributes</a></h1> -All resolvers of the same type share some common attributes detailed here: +<h1><a name="common">Common features and attributes</a></h1> +All resolvers of the same type share some common features and attributes detailed here.<br class="xooki-br"/><h2>Features</h2> +<h3>validation</h3> +All standard resolvers support several options for validation.<br class="xooki-br"/><br class="xooki-br"/>The validate attribute is used to configure if Ivy files should be checked against the Ivy file xml schema.<br class="xooki-br"/><br class="xooki-br"/>The checkconsistency attribute allow to enable or disable consistency checking between what is expected by Ivy when it finds a module descriptor, and what the module descriptor actually contains.<br class="xooki-br"/><br class="xooki-br"/>The descriptor attribute let one define if module descriptors are mandatory or optional.<br class="xooki-br"/><br class="xooki-br"/>The checksums attribute is used to define the list of checksums files to use to check the content of downloaded files has not been corrupted (eg during transfer).<br class="xooki-br"/><h3>force</h3> +Any standard resolver can be used in force mode, which is used mainly to handle local development builds. In force mode, the resolver attempts to find a dependency whatever the requested revision is (internally it replace the requested revision by 'latest.integration'), and if it finds one, it forces this revision to be returned, even when used in a chain with returnFirst=false.<br class="xooki-br"/><br class="xooki-br"/>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.<br class="xooki-br"/><span class="since">since 2.0</span> + +<h2>Attributes</h2> <table class="ivy-attributes"> <thead> <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th><th>Composite</th><th>Standard</th></tr> @@ -149,6 +154,11 @@ <td>Yes</td> <td>Yes</td> </tr> + <tr><td>force</td><td>Indicates if this resolver should be used in force mode (see above). <span class="since">since 2.0</span></td> + <td>No, defaults to false</td> + <td>No</td> + <td>Yes</td> + </tr> <tr><td>checkmodified</td><td>Indicates if this resolver should check lastmodified date to know if an ivy file is up to date.</td> <td>No, defaults to ${ivy.resolver.default.check.modified}</td> <td>No</td> @@ -179,8 +189,8 @@ <td>No</td> <td>Yes</td> </tr> - <tr><td>descriptor</td><td>optional if a module descriptor (usually an ivy file) is optional for this resolver, required to refuse modules without module descriptor <span class="since">since 2.0</span></td> - <td>No, defaults to optional</td> + <tr><td>descriptor</td><td>'optional' if a module descriptor (usually an ivy file) is optional for this resolver, 'required' to refuse modules without module descriptor <span class="since">since 2.0</span></td> + <td>No, defaults to 'optional'</td> <td>No (except dual)</td> <td>Yes</td> </tr>
Added: ant/ivy/site/target/history/trunk/images/ivy-terminology.odg URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/trunk/images/ivy-terminology.odg?rev=675851&view=auto ============================================================================== Binary file - no diff available. Propchange: ant/ivy/site/target/history/trunk/images/ivy-terminology.odg ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: ant/ivy/site/target/history/trunk/images/ivy-terminology.png URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/trunk/images/ivy-terminology.png?rev=675851&view=auto ============================================================================== Binary file - no diff available. Propchange: ant/ivy/site/target/history/trunk/images/ivy-terminology.png ------------------------------------------------------------------------------ svn:mime-type = image/png
