ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xav...@apache.org
Subject svn commit: r673341 [6/26] - in /ant/ivy/site/target: ./ history/trunk/ history/trunk/configuration/ history/trunk/images/ history/trunk/ivyfile/ history/trunk/resolver/ history/trunk/samples/ history/trunk/use/ style/
Date Wed, 02 Jul 2008 10:03:33 GMT
Modified: ant/ivy/site/target/history/trunk/ivyfile/artifact-exclude.html
URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/trunk/ivyfile/artifact-exclude.html?rev=673341&r1=673340&r2=673341&view=diff
==============================================================================
--- ant/ivy/site/target/history/trunk/ivyfile/artifact-exclude.html (original)
+++ ant/ivy/site/target/history/trunk/ivyfile/artifact-exclude.html Wed Jul  2 03:03:31 2008
@@ -97,7 +97,7 @@
 		<div id="main">
 
 		<h1 class="title">exclude</h1>
-            <br class="xooki-br"/><b>Tag:</b> exclude <b>Parent:</b>
<a href="../ivyfile/dependency.html">dependency</a><br class="xooki-br"/><br
class="xooki-br"/>This feature gives you more control on a dependency for which you do
not control its ivy file. <br class="xooki-br"/>It enables to restrict the artifacts
required, by excluding artifacts being published by the dependency or any of its transitive
dependencies, <br class="xooki-br"/>even if configuration does not a good separation
of published artifacts<br class="xooki-br"/><br class="xooki-br"/>The same principle
concerning configuration as for include applies to this exclude feature (see above the include
feature).<br class="xooki-br"/><br class="xooki-br"/>Note that exclusion is always
done AFTER inclusion has been done.<br class="xooki-br"/><br class="xooki-br"/><span
class="since">since 1.3</span> This exclude feature can also be used not only to
exclude artifacts but also to exclude whole modules. Indeed when 
 you exclude artifacts, it doesn't avoid ivy to search for the module itself, and to resolve
the dependencies of the module. But you can also exclude the whole module, which means that
the module will not be downloaded at all, and so its own dependencies will not be resolved.
For sure, this is usually done to exclude not a direct dependency but an indirect one. To
exclude a whole module, you just have to not specify any artifact name, type and ext in your
exclude rule. For instance:
+            <br class="xooki-br"/><b>Tag:</b> exclude <b>Parent:</b>
<a href="../ivyfile/dependency.html">dependency</a><br class="xooki-br"/><br
class="xooki-br"/>This feature gives you more control on a dependency for which you do
not control its ivy file. <br class="xooki-br"/>It enables to restrict the artifacts
required, by excluding artifacts being published by the dependency or any of its transitive
dependencies, <br class="xooki-br"/>even if configuration does not a good separation
of published artifacts<br class="xooki-br"/><br class="xooki-br"/>The same principle
concerning configuration as for include applies to this exclude feature (see the <a href="../../../history/trunk/ivyfile/dependency-include.html">include</a>
feature).<br class="xooki-br"/><br class="xooki-br"/>Note that exclusion is always
done AFTER inclusion has been done.<br class="xooki-br"/><br class="xooki-br"/><span
class="since">since 1.3</span> This exclude feature can also be used not only to
ex
 clude artifacts but also to exclude whole modules. Indeed when you exclude artifacts, it
doesn't avoid ivy to search for the module itself, and to resolve the dependencies of the
module. But you can also exclude the whole module, which means that the module will not be
downloaded at all, and so its own dependencies will not be resolved. For sure, this is usually
done to exclude not a direct dependency but an indirect one. To exclude a whole module, you
just have to not specify any artifact name, type and ext in your exclude rule. For instance:
 <pre>
 &lt;dependency name="A" rev="1.0"&gt;<br class="xooki-br"/>  &lt;exclude
module="B"/&gt;<br class="xooki-br"/>&lt;/dependency&gt;
 </pre>
@@ -120,7 +120,7 @@
         <td>No, defaults to type</td></tr>
     <tr><td>matcher</td><td>the <a href="../concept.html#matcher">matcher</a>
to use to match the modules to excludes <span class="since">since 1.3</span></td>
         <td>No, defaults to exactOrRegexp in pre 1.3 ivy files, and exact in 1.3 and
superior</td></tr>
-    <tr><td>conf</td><td>comma separated list of the master configurations
in which this artifact should be included.<br class="xooki-br"/>    '*' wildcard can
be used to designate all configurations of this module</td>
+    <tr><td>conf</td><td>comma separated list of the master configurations
in which this artifact should be excluded.<br class="xooki-br"/>    '*' wildcard can
be used to designate all configurations of this module</td>
         <td>No, defaults to '*', unless nested conf are specified</td></tr>
 </tbody>
 </table>
@@ -130,7 +130,7 @@
     <tr><th class="ivy-chld">Element</th><th class="ivy-chld-desc">Description</th><th
class="ivy-chld-card">Cardinality</th></tr>
 </thead>
 <tbody>
-    <tr><td><a href="../ivyfile/artifact-exclude-conf.html">conf</a></td><td>configuration
in which the artifact should be included</td>
+    <tr><td><a href="../ivyfile/artifact-exclude-conf.html">conf</a></td><td>configuration
in which the artifact should be excluded</td>
         <td>0..n</td></tr>
 </tbody>
 </table>



Mime
View raw message