incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xav...@apache.org
Subject svn commit: r536488 [16/19] - in /incubator/ivy/core/trunk: ./ doc/ doc/doc/ doc/doc/configuration/ doc/doc/configuration/macrodef/ doc/doc/configuration/namespace/ doc/doc/ivyfile/ doc/doc/releasenotes/ doc/doc/resolver/ doc/doc/tutorial/ doc/doc/tuto...
Date Wed, 09 May 2007 10:58:16 GMT
Modified: incubator/ivy/core/trunk/doc/doc/use/deliver.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/deliver.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/deliver.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/deliver.html Wed May  9 03:58:10 2007
@@ -1,111 +1,111 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
 	<textarea id="xooki-source">
-Delivers a resolved ivy file of the current module, and possibly do recursive delivery of dependencies. 
-This task does two main things:
-<h2>Generate a resolved ivy file</h2>
-This task generates a resolved ivy file of the current module, based upon the last resolve done. The resolved ivy file contains updated information about the delivered module, such as revision and status.
-
-Moreover, all included configurations files are included in the ivy file, and variables are replaced by their values.
-
-Finally, in the resolved ivy file, dynamic revisions are replaced by the static ones that have been found during the resolve step, so the ivy file can be used later safely to obtain the same dependencies (providing that a revision uniquely identifies a module, which should be the case for proper ivy use).
-
-<span class="since">since 1.3</span> The replacement of dynamic revisions by static ones can be turned off, so that dynamic revisions are kept in the ivy file.
-<h2>do recursive delivery</h2>
-This is done only if a deliver target is given to the deliver task.
-
-If a deliver target is set, then it is called (via an antcall) for each dependency which has not a suffisant status compared to the deliver status set for this task. This means that if you deliver an integration revision, no recursive delivery will be done.
-
-If you deliver a milestone or a release revision, deliver target will be called with each integration dependency. 
-
-The deliver target is called with the following properties available:
-<ul>
-  <li>dependency.name</li>
-the name of the dependency to recursively deliver
-  <li>dependency.published.status</li>
-the status to which the dependency should be delivered
-  <li>dependency.published.version</li>
-the revision to which the dependency should be delivered
-  <li>dependency.version</li>
-the revision of the dependency that should be delivered (the one that was retrieved during last resolve)
-</ul>
-Both <code>dependency.published.status</code> and <code>dependency.published.version</code> can be either asked to the user through ant input tasks (default behaviour), or be always the same for the whole recursive delivery process if the following properties are set:
-<ul>
-<li>recursive.delivery.status</li>set to the status to which all dependencies requiring to be delivered will be
-<li>recursive.delivery.version</li>set to the version to which all dependencies requiring to be delivered will be
-</ul>
-
-Usually the deliver target itself triggers an another ant build (using ant task) even if this is up to you to decide.
-
-The delivered ivy file will update its dependency revisions with those given here.  
-
-<h2>deliver and publish</h2>
-The deliver task is most of the time not called explicitly, but rather called automatically by the [[ant:publish]] task. So, when shall the deliver task be called explictly? When you actually need to separate what is performed by the deliver task (see above), from what is performed by the publish task, i.e. upload a module to a repository.
-
-And this can be particularly useful if you want to process the generated ivy file before uploading it (if you want to add automatically more information like an SCM tag used, the user who performed the release, ...).
-
-It can also be useful if you want to trigger a recursive delivery and then ensure that you get the recursively delivered modules as dependencies. In this case your build order may look like this:
-- ivy:configure
-- ivy:resolve
-- ivy:deliver with recursive delivery
-- ivy:resolve again with the ivy file generated by the recursive delivery
-- do your build stuff (compile, jar, whatever)
-- ivy:publish 
-  
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>deliverpattern</td><td>the pattern to use for ivy file delivery</td>
-        <td>No. Defaults to ${ivy.deliver.ivy.pattern}</td></tr>
-    <tr><td>pubrevision</td><td>the revision to use for the publication</td>
-        <td>No. Defaults to ${ivy.deliver.revision} if set, or the revision resolved if set, or a timestamp</td></tr>
-    <tr><td>pubdate</td><td>the publication date to use for the publication. This date should be either 'now', or a date given with the following pattern: yyyyMMddHHmmss</td>
-        <td>No. Defaults to 'now'</td></tr>
-    <tr><td>status</td><td>the status to use for the publication</td>
-        <td>No. Defaults to ${ivy.status}</td></tr>
-    <tr><td>delivertarget</td><td>the target to call for recursive delivery</td>
-        <td>No. No recursive delivery is done by default</td></tr>
-    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
-        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
-    <tr><td>replacedynamicrev</td><td>true to replace dynmic revisions by static ones in the delivered file, false to avoid this replacement <span class="since">since 1.3</span></td>
-        <td>No. Defaults to true</td></tr>
-    <tr><td>conf</td><td>comma-separated list of configurations to include in the delivered file. Accepts wildcards. <span class="since">since 2.0</span></td>
-        <td>No. Defaults to all configurations</td></tr>
-</tbody>
-</table>
-
-<h1>Example</h1>
-Deliver an ivy file without the private configurations:
-<code type="xml">
-<deliver conf="*(public)" /> 
-</code>
-</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+Delivers a resolved ivy file of the current module, and possibly do recursive delivery of dependencies. 
+This task does two main things:
+<h2>Generate a resolved ivy file</h2>
+This task generates a resolved ivy file of the current module, based upon the last resolve done. The resolved ivy file contains updated information about the delivered module, such as revision and status.
+
+Moreover, all included configurations files are included in the ivy file, and variables are replaced by their values.
+
+Finally, in the resolved ivy file, dynamic revisions are replaced by the static ones that have been found during the resolve step, so the ivy file can be used later safely to obtain the same dependencies (providing that a revision uniquely identifies a module, which should be the case for proper ivy use).
+
+<span class="since">since 1.3</span> The replacement of dynamic revisions by static ones can be turned off, so that dynamic revisions are kept in the ivy file.
+<h2>do recursive delivery</h2>
+This is done only if a deliver target is given to the deliver task.
+
+If a deliver target is set, then it is called (via an antcall) for each dependency which has not a suffisant status compared to the deliver status set for this task. This means that if you deliver an integration revision, no recursive delivery will be done.
+
+If you deliver a milestone or a release revision, deliver target will be called with each integration dependency. 
+
+The deliver target is called with the following properties available:
+<ul>
+  <li>dependency.name</li>
+the name of the dependency to recursively deliver
+  <li>dependency.published.status</li>
+the status to which the dependency should be delivered
+  <li>dependency.published.version</li>
+the revision to which the dependency should be delivered
+  <li>dependency.version</li>
+the revision of the dependency that should be delivered (the one that was retrieved during last resolve)
+</ul>
+Both <code>dependency.published.status</code> and <code>dependency.published.version</code> can be either asked to the user through ant input tasks (default behaviour), or be always the same for the whole recursive delivery process if the following properties are set:
+<ul>
+<li>recursive.delivery.status</li>set to the status to which all dependencies requiring to be delivered will be
+<li>recursive.delivery.version</li>set to the version to which all dependencies requiring to be delivered will be
+</ul>
+
+Usually the deliver target itself triggers an another ant build (using ant task) even if this is up to you to decide.
+
+The delivered ivy file will update its dependency revisions with those given here.  
+
+<h2>deliver and publish</h2>
+The deliver task is most of the time not called explicitly, but rather called automatically by the [[ant:publish]] task. So, when shall the deliver task be called explictly? When you actually need to separate what is performed by the deliver task (see above), from what is performed by the publish task, i.e. upload a module to a repository.
+
+And this can be particularly useful if you want to process the generated ivy file before uploading it (if you want to add automatically more information like an SCM tag used, the user who performed the release, ...).
+
+It can also be useful if you want to trigger a recursive delivery and then ensure that you get the recursively delivered modules as dependencies. In this case your build order may look like this:
+- ivy:configure
+- ivy:resolve
+- ivy:deliver with recursive delivery
+- ivy:resolve again with the ivy file generated by the recursive delivery
+- do your build stuff (compile, jar, whatever)
+- ivy:publish 
+  
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>deliverpattern</td><td>the pattern to use for ivy file delivery</td>
+        <td>No. Defaults to ${ivy.deliver.ivy.pattern}</td></tr>
+    <tr><td>pubrevision</td><td>the revision to use for the publication</td>
+        <td>No. Defaults to ${ivy.deliver.revision} if set, or the revision resolved if set, or a timestamp</td></tr>
+    <tr><td>pubdate</td><td>the publication date to use for the publication. This date should be either 'now', or a date given with the following pattern: yyyyMMddHHmmss</td>
+        <td>No. Defaults to 'now'</td></tr>
+    <tr><td>status</td><td>the status to use for the publication</td>
+        <td>No. Defaults to ${ivy.status}</td></tr>
+    <tr><td>delivertarget</td><td>the target to call for recursive delivery</td>
+        <td>No. No recursive delivery is done by default</td></tr>
+    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
+        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
+    <tr><td>replacedynamicrev</td><td>true to replace dynmic revisions by static ones in the delivered file, false to avoid this replacement <span class="since">since 1.3</span></td>
+        <td>No. Defaults to true</td></tr>
+    <tr><td>conf</td><td>comma-separated list of configurations to include in the delivered file. Accepts wildcards. <span class="since">since 2.0</span></td>
+        <td>No. Defaults to all configurations</td></tr>
+</tbody>
+</table>
+
+<h1>Example</h1>
+Deliver an ivy file without the private configurations:
+<code type="xml">
+<deliver conf="*(public)" /> 
+</code>
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/deliver.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/findrevision.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/findrevision.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/findrevision.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/findrevision.html Wed May  9 03:58:10 2007
@@ -1,69 +1,69 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<span class="since">since 1.4</span>
-Finds the latest revision of a module matching a given version constraint.
-
-A version constraint is what is used when declaring a <a href="../../doc/ivyfile/dependency.html">dependency</a> on a module.
-If the module is not found the property is not set.
-
-<h1>Attributes</h1>
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>organisation</td><td>the organisation of the module to find</td>
-        <td>Yes</td></tr>
-    <tr><td>module</td><td>the the name of the module to find</td>
-        <td>Yes</td></tr>
-    <tr><td>branch</td><td>the branch of the module to find</td>
-        <td>No, defaults to the default branch for the given module</td></tr>
-    <tr><td>revision</td><td>the revision constraint to apply</td>
-        <td>Yes</td></tr>
-    <tr><td>property</td><td>the property to set with the found revision</td>
-        <td>No, defaults to ivy.revision</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<ivy:findrevision organisation="apache" module="ivy" revision="latest.integration"/>
-</code>
-finds the latest version of ivy available in the repository and sets the property ivy.revision according to what was found.
-
-<hr/>
-
-<code type="xml">
-<ivy:findrevision organisation="apache" module="ivy" revision="1.0+"/>
-</code>
-same as above but only with 1.0 sub versions.
-
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<span class="since">since 1.4</span>
+Finds the latest revision of a module matching a given version constraint.
+
+A version constraint is what is used when declaring a <a href="../../doc/ivyfile/dependency.html">dependency</a> on a module.
+If the module is not found the property is not set.
+
+<h1>Attributes</h1>
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>organisation</td><td>the organisation of the module to find</td>
+        <td>Yes</td></tr>
+    <tr><td>module</td><td>the the name of the module to find</td>
+        <td>Yes</td></tr>
+    <tr><td>branch</td><td>the branch of the module to find</td>
+        <td>No, defaults to the default branch for the given module</td></tr>
+    <tr><td>revision</td><td>the revision constraint to apply</td>
+        <td>Yes</td></tr>
+    <tr><td>property</td><td>the property to set with the found revision</td>
+        <td>No, defaults to ivy.revision</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivy:findrevision organisation="apache" module="ivy" revision="latest.integration"/>
+</code>
+finds the latest version of ivy available in the repository and sets the property ivy.revision according to what was found.
+
+<hr/>
+
+<code type="xml">
+<ivy:findrevision organisation="apache" module="ivy" revision="1.0+"/>
+</code>
+same as above but only with 1.0 sub versions.
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/findrevision.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/info.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/info.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/info.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/info.html Wed May  9 03:58:10 2007
@@ -1,59 +1,59 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<span class="since">since 1.4</span>
-The info task ease the access to some essential data contained in an ivy file without performing a dependency resolution.
-
-The information is retrieved by setting ant properties:
-<table>
-<tr><td>ivy.organisation</td><td>The organisation of the module, as found in the <a href="../../doc/ivyfile/info.html">info</a> tag of the ivy file parsed</td></tr>
-<tr><td>ivy.module</td><td>The name of the module, as found in the <a href="../../doc/ivyfile/info.html">info</a> tag of the ivy file parsed</td></tr>
-<tr><td>ivy.revision</td><td>The revision of the module, as found in the <a href="../../doc/ivyfile/info.html">info</a> tag of the ivy file parsed</td></tr>
-<tr><td>ivy.configurations</td><td>A comma separated list of configurations of the module, as declared in the <a href="../../doc/ivyfile/configurations.html">configurations</a> section</td></tr>
-<tr><td>ivy.public.configurations</td><td>A comma separated list of public configurations of the module, as declared in the <a href="../../doc/ivyfile/configurations.html">configurations</a> section</td></tr>
-</table>
-
-<h1>Attributes</h1>
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>file</td><td>the ivy file to parse</td>
-        <td>Yes</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<ivy:info file="${basedir}/path/to/ivy.xml" />
-</code>
-Parses ${basedir}/path/to/ivy.xml and set properties as described above accordingly.
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<span class="since">since 1.4</span>
+The info task ease the access to some essential data contained in an ivy file without performing a dependency resolution.
+
+The information is retrieved by setting ant properties:
+<table>
+<tr><td>ivy.organisation</td><td>The organisation of the module, as found in the <a href="../../doc/ivyfile/info.html">info</a> tag of the ivy file parsed</td></tr>
+<tr><td>ivy.module</td><td>The name of the module, as found in the <a href="../../doc/ivyfile/info.html">info</a> tag of the ivy file parsed</td></tr>
+<tr><td>ivy.revision</td><td>The revision of the module, as found in the <a href="../../doc/ivyfile/info.html">info</a> tag of the ivy file parsed</td></tr>
+<tr><td>ivy.configurations</td><td>A comma separated list of configurations of the module, as declared in the <a href="../../doc/ivyfile/configurations.html">configurations</a> section</td></tr>
+<tr><td>ivy.public.configurations</td><td>A comma separated list of public configurations of the module, as declared in the <a href="../../doc/ivyfile/configurations.html">configurations</a> section</td></tr>
+</table>
+
+<h1>Attributes</h1>
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>file</td><td>the ivy file to parse</td>
+        <td>Yes</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivy:info file="${basedir}/path/to/ivy.xml" />
+</code>
+Parses ${basedir}/path/to/ivy.xml and set properties as described above accordingly.
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/info.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/install.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/install.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/install.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/install.html Wed May  9 03:58:10 2007
@@ -1,72 +1,72 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-Installs a module and all its dependencies in a resolver. <span class="since">since 1.3</span>
-
-The module to install should be available in a resolver, and will be installed in another resolver which should support publish.
-
-This is particularly useful for users who only have a private repository, and want to benefit from public repositories from time to time. In this case, when a module is missing in the private repository, a call to install let download the module from a public repository not usually used for dependency resolution, and install it and its dependencies in the private repository.
-
-For more details about this task and its usage see the <a href="../../doc/tutorial/build-repository.html">build repository tutorial</a>
-  
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>from</td><td>the name of the resolver in which the module must be found</td>
-        <td>Yes</td></tr>
-    <tr><td>to</td><td>the name of the resolver in which the module must be installed</td>
-        <td>Yes</td></tr>
-    <tr><td>organisation</td><td>the name of the organisation of the module to install</td>
-        <td>Yes</td></tr>
-    <tr><td>module</td><td>the name of the module to install</td>
-        <td>Yes</td></tr>
-    <tr><td>revision</td><td>the revision of the module to install</td>
-        <td>Yes</td></tr>
-    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
-        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
-    <tr><td>overwrite</td><td>true to override modules already present in the destination resolver, false otherwise</td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>transitive</td><td>true to install the module and all its transitive dependencies, false to install only the module</td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>matcher</td><td>the name of the matcher to use to find the modules to install</td>
-        <td>No, defaults to exact</td></tr>
-    <tr><td>haltonunresolved</td><td>true to fail build on unresolved dependencies <span class="since">since 2.0</span></td>
-        <td>No, defaults to true</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<ivy:install organisation="apache" module="commons-lang" revision="2.0" from="ivyrep" to="myfsresolver"/>
-</code>
-Installs the module commons-lang from apache in revision 2.0 in the resolver myfsresolver. The module is found in the resolver named 'ivyrep'.
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Installs a module and all its dependencies in a resolver. <span class="since">since 1.3</span>
+
+The module to install should be available in a resolver, and will be installed in another resolver which should support publish.
+
+This is particularly useful for users who only have a private repository, and want to benefit from public repositories from time to time. In this case, when a module is missing in the private repository, a call to install let download the module from a public repository not usually used for dependency resolution, and install it and its dependencies in the private repository.
+
+For more details about this task and its usage see the <a href="../../doc/tutorial/build-repository.html">build repository tutorial</a>
+  
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>from</td><td>the name of the resolver in which the module must be found</td>
+        <td>Yes</td></tr>
+    <tr><td>to</td><td>the name of the resolver in which the module must be installed</td>
+        <td>Yes</td></tr>
+    <tr><td>organisation</td><td>the name of the organisation of the module to install</td>
+        <td>Yes</td></tr>
+    <tr><td>module</td><td>the name of the module to install</td>
+        <td>Yes</td></tr>
+    <tr><td>revision</td><td>the revision of the module to install</td>
+        <td>Yes</td></tr>
+    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
+        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
+    <tr><td>overwrite</td><td>true to override modules already present in the destination resolver, false otherwise</td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>transitive</td><td>true to install the module and all its transitive dependencies, false to install only the module</td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>matcher</td><td>the name of the matcher to use to find the modules to install</td>
+        <td>No, defaults to exact</td></tr>
+    <tr><td>haltonunresolved</td><td>true to fail build on unresolved dependencies <span class="since">since 2.0</span></td>
+        <td>No, defaults to true</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivy:install organisation="apache" module="commons-lang" revision="2.0" from="ivyrep" to="myfsresolver"/>
+</code>
+Installs the module commons-lang from apache in revision 2.0 in the resolver myfsresolver. The module is found in the resolver named 'ivyrep'.
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/install.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/listmodules.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/listmodules.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/listmodules.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/listmodules.html Wed May  9 03:58:10 2007
@@ -1,76 +1,76 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<span class="since">since 1.4</span>
-Finds the list of modules in the repository matching some criteria and set a corresponding list of properties in ant.
-
-The criteria is set by given patterns matching the organisation, name branch and revision of the modules to find.
-
-To know if a module matches the criteria ivy will use the configured <a href="../../doc/concept#matcher.html">pattern matcher</a>.
-
-<h1>Attributes</h1>
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>organisation</td><td>the pattern matching the organisation of the modules to list</td>
-        <td>Yes</td></tr>
-    <tr><td>module</td><td>the pattern matching the name of the modules to list</td>
-        <td>Yes</td></tr>
-    <tr><td>branch</td><td>the pattern matching the branch of the modules to list</td>
-        <td>No, defaults to '*'</td></tr>
-    <tr><td>revision</td><td>the pattern matching the revision of the modules to list</td>
-        <td>Yes</td></tr>
-    <tr><td>matcher</td><td>the name of the pattern matcher to use for matching the modules fields</td>
-        <td>No. Defaults to exactOrRegexp.</td></tr>
-    <tr><td>property</td><td>the pattern of the property to set when a module is found</td>
-        <td>Yes</td></tr>
-    <tr><td>value</td><td>The pattern of the value to set when a module is found</td><td>Yes</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<ivy:listmodules organisation="apache" module="ivy" revision="*" property="ivy.[revision]" value="found"/>
-</code>
-will find all revisions of the module ivy in the org apache, and create one property for each revision found, the name of the property depending on the revision, the value being always 'found'
-
-<hr/>
-
-<code type="xml">
-<ivy:listmodules organisation="*" module="ivy*" revision="1.0" matcher="glob" property="modules.[module]" value="[organisation]"/>
-</code>
-use the glob matcher to find all modules which name starts with ivy with revision 1.0, and sets for each a property with module name found  and organisation for value.
-Example:
-modules.ivy=apache
-modules.ivyde=apache
-modules.ivytools=ivytools
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<span class="since">since 1.4</span>
+Finds the list of modules in the repository matching some criteria and set a corresponding list of properties in ant.
+
+The criteria is set by given patterns matching the organisation, name branch and revision of the modules to find.
+
+To know if a module matches the criteria ivy will use the configured <a href="../../doc/concept#matcher.html">pattern matcher</a>.
+
+<h1>Attributes</h1>
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>organisation</td><td>the pattern matching the organisation of the modules to list</td>
+        <td>Yes</td></tr>
+    <tr><td>module</td><td>the pattern matching the name of the modules to list</td>
+        <td>Yes</td></tr>
+    <tr><td>branch</td><td>the pattern matching the branch of the modules to list</td>
+        <td>No, defaults to '*'</td></tr>
+    <tr><td>revision</td><td>the pattern matching the revision of the modules to list</td>
+        <td>Yes</td></tr>
+    <tr><td>matcher</td><td>the name of the pattern matcher to use for matching the modules fields</td>
+        <td>No. Defaults to exactOrRegexp.</td></tr>
+    <tr><td>property</td><td>the pattern of the property to set when a module is found</td>
+        <td>Yes</td></tr>
+    <tr><td>value</td><td>The pattern of the value to set when a module is found</td><td>Yes</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivy:listmodules organisation="apache" module="ivy" revision="*" property="ivy.[revision]" value="found"/>
+</code>
+will find all revisions of the module ivy in the org apache, and create one property for each revision found, the name of the property depending on the revision, the value being always 'found'
+
+<hr/>
+
+<code type="xml">
+<ivy:listmodules organisation="*" module="ivy*" revision="1.0" matcher="glob" property="modules.[module]" value="[organisation]"/>
+</code>
+use the glob matcher to find all modules which name starts with ivy with revision 1.0, and sets for each a property with module name found  and organisation for value.
+Example:
+modules.ivy=apache
+modules.ivyde=apache
+modules.ivytools=ivytools
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/listmodules.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/postresolvetask.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/postresolvetask.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/postresolvetask.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/postresolvetask.html Wed May  9 03:58:10 2007
@@ -1,80 +1,80 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-Several tasks in Ivy are considered as post resolve task and share a common behaviour and settings accordingly.
-
-These tasks are:
-<ul>
-<li>[[ant:retrieve]]</li>
-<li>[[ant:cachefileset]]</li>
-<li>[[ant:cachepath]]</li>
-<li>[[ant:artifactproperty]] <span class="since">(since 2.0)</span></li>
-<li>[[ant:artifactreport]] <span class="since">(since 2.0)</span></li>
-</ul>
-
-All these tasks will trigger automatically a resolve if:
-<ul>
-<li>none has already been called in the current build with the attribute keep set to true (see below)</li>
-<li>organisation and module are not set</li>
-</ul>
-
-Since Ivy 1.4, there are two ways to run a [[ant:resolve]]: with an ivy file, or with the inline mode.
-When you call resolve with an ivy file, the default for it is to keep the resolved data for use by the subsequent post resolve tasks. When you run an inline resolve, the default is not to keep the data. Youo can override this behaviour by setting the keep attribute as you like.
-
-If you want to to reuse the resolved data obtained through a call to resolve in another build (i.e. not the current one), then you have to set the organisation and module attributes. This work only if the cache was not cleaned since your last resolve call. This does not work with inline calls, which must be performed in the same build.
-
-The attributes listed are then mostly used only if a resolve is triggered automatically.
-
-<h1>Attributes</h1>
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>conf</td><td>a comma separated list of the configurations to retrieve</td>
-        <td>No. Defaults to the configurations resolved by the last resolve call, or * if no resolve was explicitly called</td></tr>
-    <tr><td>inline</td><td>true to use inline mode, false to resolve an ivy file <span class="since">since 1.4</span></td><td>No. defaults false</td></tr>
-    <tr><td>organisation</td><td>the organisation of the module to retrieve. This usually doesn't need to be set since it defaults to the last resolved one, except for inline mode where it is required.</td><td>Yes in inline mode, otherwise no, it then defaults to last resolved module name</td></tr>
-    <tr><td>module</td><td>the name of the module to retrieve. This usually doesn't need to be set since it defaults to the last resolved one, except for inline mode where it is required.</td><td>Yes in inline mode, otherwise no, it then defaults to last resolved module name</td></tr>
-    <tr><td>revision</td><td>the revision constraint of the module to retrieve. Used only in inline mode. <span class="since">since 1.4</span></td><td>No. Defaults to latest.integration</td></tr>
-    <tr><td>transitive</td><td>true to resolve dependencies transitively, false otherwise <span class="since">since 1.4</span></td><td>No. Defaults to true</td></tr>
-    <tr><td>haltonfailure</td><td>true to halt the build on ivy failure, false to continue</td><td>No. Defaults to true</td></tr>
-    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td><td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
-    <tr><td>file</td><td>the file to resolve if a resolve is necessary <span class="since">since 2.0</span></td><td>No. Defaults to the previous resolved Ivy file or to ${ivy.dep.file}</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<ivy:cachepath organisation="emma" module="emma" revision="2.0.4217" inline="true" conf="ant" pathid="emma.classpath"/>
-<taskdef resource="emma_ant.properties" classpathref="emma.classpath" /> 
-</code>
-Resolves the emma module in version 2.0.4217, constructs an ant path with the corresponding artifacts, and then define the emma tasks using this path.
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Several tasks in Ivy are considered as post resolve task and share a common behaviour and settings accordingly.
+
+These tasks are:
+<ul>
+<li>[[ant:retrieve]]</li>
+<li>[[ant:cachefileset]]</li>
+<li>[[ant:cachepath]]</li>
+<li>[[ant:artifactproperty]] <span class="since">(since 2.0)</span></li>
+<li>[[ant:artifactreport]] <span class="since">(since 2.0)</span></li>
+</ul>
+
+All these tasks will trigger automatically a resolve if:
+<ul>
+<li>none has already been called in the current build with the attribute keep set to true (see below)</li>
+<li>organisation and module are not set</li>
+</ul>
+
+Since Ivy 1.4, there are two ways to run a [[ant:resolve]]: with an ivy file, or with the inline mode.
+When you call resolve with an ivy file, the default for it is to keep the resolved data for use by the subsequent post resolve tasks. When you run an inline resolve, the default is not to keep the data. Youo can override this behaviour by setting the keep attribute as you like.
+
+If you want to to reuse the resolved data obtained through a call to resolve in another build (i.e. not the current one), then you have to set the organisation and module attributes. This work only if the cache was not cleaned since your last resolve call. This does not work with inline calls, which must be performed in the same build.
+
+The attributes listed are then mostly used only if a resolve is triggered automatically.
+
+<h1>Attributes</h1>
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>conf</td><td>a comma separated list of the configurations to retrieve</td>
+        <td>No. Defaults to the configurations resolved by the last resolve call, or * if no resolve was explicitly called</td></tr>
+    <tr><td>inline</td><td>true to use inline mode, false to resolve an ivy file <span class="since">since 1.4</span></td><td>No. defaults false</td></tr>
+    <tr><td>organisation</td><td>the organisation of the module to retrieve. This usually doesn't need to be set since it defaults to the last resolved one, except for inline mode where it is required.</td><td>Yes in inline mode, otherwise no, it then defaults to last resolved module name</td></tr>
+    <tr><td>module</td><td>the name of the module to retrieve. This usually doesn't need to be set since it defaults to the last resolved one, except for inline mode where it is required.</td><td>Yes in inline mode, otherwise no, it then defaults to last resolved module name</td></tr>
+    <tr><td>revision</td><td>the revision constraint of the module to retrieve. Used only in inline mode. <span class="since">since 1.4</span></td><td>No. Defaults to latest.integration</td></tr>
+    <tr><td>transitive</td><td>true to resolve dependencies transitively, false otherwise <span class="since">since 1.4</span></td><td>No. Defaults to true</td></tr>
+    <tr><td>haltonfailure</td><td>true to halt the build on ivy failure, false to continue</td><td>No. Defaults to true</td></tr>
+    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td><td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
+    <tr><td>file</td><td>the file to resolve if a resolve is necessary <span class="since">since 2.0</span></td><td>No. Defaults to the previous resolved Ivy file or to ${ivy.dep.file}</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivy:cachepath organisation="emma" module="emma" revision="2.0.4217" inline="true" conf="ant" pathid="emma.classpath"/>
+<taskdef resource="emma_ant.properties" classpathref="emma.classpath" /> 
+</code>
+Resolves the emma module in version 2.0.4217, constructs an ant path with the corresponding artifacts, and then define the emma tasks using this path.
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/postresolvetask.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/publish.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/publish.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/publish.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/publish.html Wed May  9 03:58:10 2007
@@ -1,86 +1,86 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
 	<textarea id="xooki-source">
-Publishes the current modules artifacts.
-
-This task is meant to publish the declared published artifacts of the current module to a repository.
-
-The repository is given through the name of a resolver declared in current ivy configuration. See <a href="../../doc/configuration.html">configuration</a> for details about resolver supporting artifact publishing.
-It also publishes the delivered ivy file (except if you don't want), and even deliver it if it has not been done with a previous deliver call or if forcedeliver is set to true. That's why this task takes some parameters useful only for delivery.
-
-<span class="since">since 1.4.1</span>
-The source artifact pattern can be specified either as an attribute on the task (artifactspattern) or using a list of nested artifacts element (see examples below).
-  
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>artifactspattern</td><td>the pattern to use to find artifacts to publish</td>
-        <td>No. Defaults to ${ivy.publish.src.artifacts.pattern}</td></tr>
-    <tr><td>resolver</td><td>the name of the resolver to use for publication</td>
-        <td>Yes</td></tr>
-    <tr><td>pubrevision</td><td>the revision to use for the publication</td>
-        <td>No. Defaults to the ${ivy.deliver.revision}</td></tr>
-    <tr><td>forcedeliver</td><td>true to force the implicit call to deliver, false to do it only if the ivy file to publish doesn't exist yet <span class="since">since 1.4</span></td>
-        <td>No. Defaults to false</td></tr>
-    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
-        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
-    <tr><td>replacedynamicrev</td><td>true to replace dynmic revisions by static ones in the delivered file, false to avoid this replacement <span class="since">since 1.3</span></td>
-        <td>No. Defaults to true</td></tr>
-    <tr><td>publishivy</td><td>True to publish delivered ivy file, false otherwise</td>
-        <td>No. Defaults to true</td></tr>
-    <tr><td>conf</td><td>A comma separated list of configurations to publish.  <span class="since">since 1.4.1</span></td>
-        <td>No. Defaults to all configurations</td></tr>
-    <tr><td>overwrite</td><td>True to overwrite files in repository if the revision already exist, false to let it as is</td>
-        <td>No. Defaults to false</td></tr>
-    <tr><td>warnonmissing</td><td>True to warn when artifacts to be published are missing</td>
-        <td>No. Defaults to true</td></tr>
-    <tr><td>haltonmissing</td><td>True to halt build when artifacts to be published are missing</td>
-        <td>No. Defaults to true</td></tr>
-    <tr><td>srcivypattern</td><td>the pattern to use to find ivy file to publish, and even deliver if necessary (<span class="since">since 1.2</span>)</td>
-        <td>No. Defaults to the value of artifactspattern</td></tr>
-    <tr><td>pubdate</td><td>the publication date to use for the delivery, if necessary. This date should be either 'now', or a date given with the following pattern: yyyyMMddHHmmss</td>
-        <td>No. Defaults to 'now'</td></tr>
-    <tr><td>status</td><td>the status to use for the delivery, if necessary</td>
-        <td>No. Defaults to ${ivy.status}</td></tr>
-    <tr><td>delivertarget</td><td>the target to call for recursive delivery</td>
-        <td>No. No recursive delivery is done by default</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<ivy:publish resolver="local" pubrevision="1.0">
-   <artifacts pattern="1/[artifact].[ext]" />
-   <artifacts pattern="2/[artifact].[ext]" />
-</ivy:publish>
-</code>
-Publishes the last resolved module in the local resolver with revision 1.0, looking for artifacts in directories 1 and 2.
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+Publishes the current modules artifacts.
+
+This task is meant to publish the declared published artifacts of the current module to a repository.
+
+The repository is given through the name of a resolver declared in current ivy configuration. See <a href="../../doc/configuration.html">configuration</a> for details about resolver supporting artifact publishing.
+It also publishes the delivered ivy file (except if you don't want), and even deliver it if it has not been done with a previous deliver call or if forcedeliver is set to true. That's why this task takes some parameters useful only for delivery.
+
+<span class="since">since 1.4.1</span>
+The source artifact pattern can be specified either as an attribute on the task (artifactspattern) or using a list of nested artifacts element (see examples below).
+  
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>artifactspattern</td><td>the pattern to use to find artifacts to publish</td>
+        <td>No. Defaults to ${ivy.publish.src.artifacts.pattern}</td></tr>
+    <tr><td>resolver</td><td>the name of the resolver to use for publication</td>
+        <td>Yes</td></tr>
+    <tr><td>pubrevision</td><td>the revision to use for the publication</td>
+        <td>No. Defaults to the ${ivy.deliver.revision}</td></tr>
+    <tr><td>forcedeliver</td><td>true to force the implicit call to deliver, false to do it only if the ivy file to publish doesn't exist yet <span class="since">since 1.4</span></td>
+        <td>No. Defaults to false</td></tr>
+    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
+        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
+    <tr><td>replacedynamicrev</td><td>true to replace dynmic revisions by static ones in the delivered file, false to avoid this replacement <span class="since">since 1.3</span></td>
+        <td>No. Defaults to true</td></tr>
+    <tr><td>publishivy</td><td>True to publish delivered ivy file, false otherwise</td>
+        <td>No. Defaults to true</td></tr>
+    <tr><td>conf</td><td>A comma separated list of configurations to publish.  <span class="since">since 1.4.1</span></td>
+        <td>No. Defaults to all configurations</td></tr>
+    <tr><td>overwrite</td><td>True to overwrite files in repository if the revision already exist, false to let it as is</td>
+        <td>No. Defaults to false</td></tr>
+    <tr><td>warnonmissing</td><td>True to warn when artifacts to be published are missing</td>
+        <td>No. Defaults to true</td></tr>
+    <tr><td>haltonmissing</td><td>True to halt build when artifacts to be published are missing</td>
+        <td>No. Defaults to true</td></tr>
+    <tr><td>srcivypattern</td><td>the pattern to use to find ivy file to publish, and even deliver if necessary (<span class="since">since 1.2</span>)</td>
+        <td>No. Defaults to the value of artifactspattern</td></tr>
+    <tr><td>pubdate</td><td>the publication date to use for the delivery, if necessary. This date should be either 'now', or a date given with the following pattern: yyyyMMddHHmmss</td>
+        <td>No. Defaults to 'now'</td></tr>
+    <tr><td>status</td><td>the status to use for the delivery, if necessary</td>
+        <td>No. Defaults to ${ivy.status}</td></tr>
+    <tr><td>delivertarget</td><td>the target to call for recursive delivery</td>
+        <td>No. No recursive delivery is done by default</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivy:publish resolver="local" pubrevision="1.0">
+   <artifacts pattern="1/[artifact].[ext]" />
+   <artifacts pattern="2/[artifact].[ext]" />
+</ivy:publish>
+</code>
+Publishes the last resolved module in the local resolver with revision 1.0, looking for artifacts in directories 1 and 2.
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/publish.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/report.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/report.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/report.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/report.html Wed May  9 03:58:10 2007
@@ -1,99 +1,99 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-Generates reports of dependency resolving. One report per configuration is generated, but all reports generated together are hyperlinked one to each other.
-
-This task should be used only after a call to resolve, even if the call was not done during the same ant build.
-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 <a href="../../samples/jayasoft-ivyrep-example-default.html">example</a>.
-
-The task also generates a graphml file which can be loaded with the free <a href="http://www.yworks.com/en/products_yed_about.htm">yEd</a> graph editor.
-Then following a few <a href="../../doc/yed.html">simple steps</a> you can obtain a graph like this <a href="../../samples/jayasoft-ivyrep-example-default.jpg">one</a>.
-
-<div class="since">since 1.4</div> If a custom XSL is specified, it's possible to specify additional parameters to the stylesheet.
-
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>todir</td><td>the directory to which reports should be generated</td>
-        <td>No, defaults to ${ivy.report.todir}, or execution directory if not defined</td></tr>
-    <tr><td>outputpattern</td><td>the generated report names pattern</td>
-        <td>No, defaults to ${ivy.report.output.pattern}, or [organisation]-[module]-[conf].[ext] if not defined</td></tr>
-    <tr><td>xsl</td><td>true to generate a report (by default html report) using xslt, false otherwise <span class="since">since 1.3</span></td>
-        <td>No, defaults to true</td></tr>
-    <tr><td>xml</td><td>true to generate a xml report, false otherwise <span class="since">since 1.3</span></td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>graph</td><td>true to generate graphml files, false otherwise</td>
-        <td>No, defaults to true</td></tr>
-    <tr><td>dot</td><td>true to generate <a href="http://www.graphviz.org/">graphviz dot</a> files, false otherwise <span class="since">since 1.4</span></td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>conf</td><td>a comma separated list of the configurations for which a report should be generated</td>
-        <td>No. Defaults to the configurations resolved by the last resolve call (during same ant build), or ${ivy.resolved.configurations} if no resolve was called</td></tr>
-    <tr><td>organisation</td><td>the name of the organisation of the module for which report should be generated</td>
-        <td>No, unless no resolve was called during the build. Defaults to last resolved module organisation.</td></tr>
-    <tr><td>module</td><td>the name of the module for which report should be generated</td>
-        <td>No, unless no resolve was called during the build. Defaults to last resolved module.</td></tr>
-    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
-        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
-    <tr><td>xslfile</td><td>indicates which xsl file should be used to generate the report</td>
-        <td>No, defaults to ivy provided xsl which generates html report</td></tr>
-</tbody>
-</table>
-
-<h1>Examples</h1>
-To generate a HTML and graphml report:
-<code type="xml">
-<report conf="compile" />
-</code>
-
-<hr/>
-To generate a HTML report only:
-<code type="xml">
-<report conf="compile" graph="false" />
-</code>
-
-<hr/>
-To generate an XML report using a custom stylesheet:
-<code type="xml">
-<report conf="compile" xslfile="my-custom-stylesheet.xsl" xslext="xml" />
-</code>
-
-To generate an XML report using a custom stylesheet which needs some parameters:
-<code type="xml">
-<report conf="compile" xslfile="my-custom-stylesheet.xsl" xslext="xml">
-    <param name="param1" expression="value1" /> 
-    <param name="param2" expression="value2" /> 
-</report>
-</code>
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Generates reports of dependency resolving. One report per configuration is generated, but all reports generated together are hyperlinked one to each other.
+
+This task should be used only after a call to resolve, even if the call was not done during the same ant build.
+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 <a href="../../samples/jayasoft-ivyrep-example-default.html">example</a>.
+
+The task also generates a graphml file which can be loaded with the free <a href="http://www.yworks.com/en/products_yed_about.htm">yEd</a> graph editor.
+Then following a few <a href="../../doc/yed.html">simple steps</a> you can obtain a graph like this <a href="../../samples/jayasoft-ivyrep-example-default.jpg">one</a>.
+
+<div class="since">since 1.4</div> If a custom XSL is specified, it's possible to specify additional parameters to the stylesheet.
+
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>todir</td><td>the directory to which reports should be generated</td>
+        <td>No, defaults to ${ivy.report.todir}, or execution directory if not defined</td></tr>
+    <tr><td>outputpattern</td><td>the generated report names pattern</td>
+        <td>No, defaults to ${ivy.report.output.pattern}, or [organisation]-[module]-[conf].[ext] if not defined</td></tr>
+    <tr><td>xsl</td><td>true to generate a report (by default html report) using xslt, false otherwise <span class="since">since 1.3</span></td>
+        <td>No, defaults to true</td></tr>
+    <tr><td>xml</td><td>true to generate a xml report, false otherwise <span class="since">since 1.3</span></td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>graph</td><td>true to generate graphml files, false otherwise</td>
+        <td>No, defaults to true</td></tr>
+    <tr><td>dot</td><td>true to generate <a href="http://www.graphviz.org/">graphviz dot</a> files, false otherwise <span class="since">since 1.4</span></td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>conf</td><td>a comma separated list of the configurations for which a report should be generated</td>
+        <td>No. Defaults to the configurations resolved by the last resolve call (during same ant build), or ${ivy.resolved.configurations} if no resolve was called</td></tr>
+    <tr><td>organisation</td><td>the name of the organisation of the module for which report should be generated</td>
+        <td>No, unless no resolve was called during the build. Defaults to last resolved module organisation.</td></tr>
+    <tr><td>module</td><td>the name of the module for which report should be generated</td>
+        <td>No, unless no resolve was called during the build. Defaults to last resolved module.</td></tr>
+    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
+        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
+    <tr><td>xslfile</td><td>indicates which xsl file should be used to generate the report</td>
+        <td>No, defaults to ivy provided xsl which generates html report</td></tr>
+</tbody>
+</table>
+
+<h1>Examples</h1>
+To generate a HTML and graphml report:
+<code type="xml">
+<report conf="compile" />
+</code>
+
+<hr/>
+To generate a HTML report only:
+<code type="xml">
+<report conf="compile" graph="false" />
+</code>
+
+<hr/>
+To generate an XML report using a custom stylesheet:
+<code type="xml">
+<report conf="compile" xslfile="my-custom-stylesheet.xsl" xslext="xml" />
+</code>
+
+To generate an XML report using a custom stylesheet which needs some parameters:
+<code type="xml">
+<report conf="compile" xslfile="my-custom-stylesheet.xsl" xslext="xml">
+    <param name="param1" expression="value1" /> 
+    <param name="param2" expression="value2" /> 
+</report>
+</code>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/use/report.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/use/repreport.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/use/repreport.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/use/repreport.html (original)
+++ incubator/ivy/core/trunk/doc/doc/use/repreport.html Wed May  9 03:58:10 2007
@@ -1,114 +1,114 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-Generates reports about dependencies among several modules in the repository (repreport stands for repository report).<span class="since">since 1.4</span>
-
-This task is similar to the [[ant:report]] task, except that instead of working on a single module you just resolved, it works with a set of modules in your repository.
-
-Note that the set of modules for which you generate the report is determined by setting organisation module and revision and using a matcher, but also by the dependencies of these modules. No dependency is excluded.
-
-Usually the most useful report is a graph, you can generate either a graphml file that you can then easily <a href="../../doc/yed.html">layout using yEd</a>, or a dot file which is the format recognized by graphviz, which is a free tool which does automatic graph layout, and can thus be used to generate automatically a GIF or PNG of the dependencies between all your modules.
-
-<table class="ant">
-<thead>
-    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
-</thead>
-<tbody>
-    <tr><td>organisation</td><td>A pattern matching the organisation of the modules for which the report should be generated</td>
-        <td>No, defaults to '*'</td></tr>
-    <tr><td>module</td><td>A pattern matching the name of the modules for which the report should be generated</td>
-        <td>No, defaults to '*'</td></tr>
-    <tr><td>branch</td><td>The name of the branch of the modules for which the report should be generated</td>
-        <td>No, defaults to no branch specified</td></tr>
-    <tr><td>revision</td><td>The revision of the modules for which the report should be generated. Only one revision per module will be used, so most of the time keeping the default (latest.integration) is the best thing to do, because it's not very easy to specify only one revision for several modules.</td>
-        <td>No, defaults to 'latest.integration'</td></tr>
-    <tr><td>todir</td><td>the directory to which reports should be generated</td>
-        <td>No, defaults to execution directory</td></tr>
-    <tr><td>outputname</td><td>the name to use for the generate file (without extension)</td>
-        <td>No, defaults to ivy-repository-report</td></tr>
-    <tr><td>xml</td><td>true to generate a xml report, false otherwise</td>
-        <td>No, defaults to true</td></tr>
-    <tr><td>xsl</td><td>true to generate a report using xslt, false otherwise</td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>xslfile</td><td>indicates which xsl file should be used to generate the report</td>
-        <td>Yes if you want to use xsl transformation</td></tr>
-    <tr><td>xslext</td><td>indicates the extension to use when generating report using xsl</td>
-        <td>No defaults to 'html'</td></tr>
-    <tr><td>graph</td><td>true to generate graphml file, false otherwise</td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>dot</td><td>true to generate graphviz dot format file, false otherwise</td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>matcher</td><td>the name of the matcher to use for matching modules names and organisations in your repository</td>
-        <td>No. Defaults to exactOrRegexp</td></tr>
-    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
-        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
-</tbody>
-</table>
-
-<h1>Examples</h1>
-To generate a xml report for all the latest versions of all the modules in your repository:
-<code type="xml">
-<ivy:repreport />
-</code>
-
-<hr/>
-To generate a graphml report for all the latest versions of all the modules in your repository:
-<code type="xml">
-<ivy:repreport xml="false" graph="true" />
-</code>
-
-<hr/>
-To generate a xml report for all the latest versions of the modules from the organisation foo in your repository:
-<code type="xml">
-<ivy:repreport organisation="foo" />
-</code>
-
-<hr/>
-To generate a xml report for all the versions on the 1.x stream of the modules named bar* from the organisation foo in your repository:
-<code type="xml">
-<ivy:repreport organisation="foo" module="bar*" revision="1.+" matcher="glob" />
-</code>
-
-<hr/>
-To generate an XML report using a custom stylesheet:
-<code type="xml">
-<ivy:repreport xsl="true" xslfile="my-custom-stylesheet.xsl" xslext="xml" />
-</code>
-
-<hr/>
-To generate an XML report using a custom stylesheet which needs some parameters:
-<code type="xml">
-<ivy:repreport xsl="true" xslfile="my-custom-stylesheet.xsl" xslext="xml">
-    <param name="param1" expression="value1" /> 
-    <param name="param2" expression="value2" /> 
-</report>
-</code>
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Generates reports about dependencies among several modules in the repository (repreport stands for repository report).<span class="since">since 1.4</span>
+
+This task is similar to the [[ant:report]] task, except that instead of working on a single module you just resolved, it works with a set of modules in your repository.
+
+Note that the set of modules for which you generate the report is determined by setting organisation module and revision and using a matcher, but also by the dependencies of these modules. No dependency is excluded.
+
+Usually the most useful report is a graph, you can generate either a graphml file that you can then easily <a href="../../doc/yed.html">layout using yEd</a>, or a dot file which is the format recognized by graphviz, which is a free tool which does automatic graph layout, and can thus be used to generate automatically a GIF or PNG of the dependencies between all your modules.
+
+<table class="ant">
+<thead>
+    <tr><th class="ant-att">Attribute</th><th class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>organisation</td><td>A pattern matching the organisation of the modules for which the report should be generated</td>
+        <td>No, defaults to '*'</td></tr>
+    <tr><td>module</td><td>A pattern matching the name of the modules for which the report should be generated</td>
+        <td>No, defaults to '*'</td></tr>
+    <tr><td>branch</td><td>The name of the branch of the modules for which the report should be generated</td>
+        <td>No, defaults to no branch specified</td></tr>
+    <tr><td>revision</td><td>The revision of the modules for which the report should be generated. Only one revision per module will be used, so most of the time keeping the default (latest.integration) is the best thing to do, because it's not very easy to specify only one revision for several modules.</td>
+        <td>No, defaults to 'latest.integration'</td></tr>
+    <tr><td>todir</td><td>the directory to which reports should be generated</td>
+        <td>No, defaults to execution directory</td></tr>
+    <tr><td>outputname</td><td>the name to use for the generate file (without extension)</td>
+        <td>No, defaults to ivy-repository-report</td></tr>
+    <tr><td>xml</td><td>true to generate a xml report, false otherwise</td>
+        <td>No, defaults to true</td></tr>
+    <tr><td>xsl</td><td>true to generate a report using xslt, false otherwise</td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>xslfile</td><td>indicates which xsl file should be used to generate the report</td>
+        <td>Yes if you want to use xsl transformation</td></tr>
+    <tr><td>xslext</td><td>indicates the extension to use when generating report using xsl</td>
+        <td>No defaults to 'html'</td></tr>
+    <tr><td>graph</td><td>true to generate graphml file, false otherwise</td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>dot</td><td>true to generate graphviz dot format file, false otherwise</td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>matcher</td><td>the name of the matcher to use for matching modules names and organisations in your repository</td>
+        <td>No. Defaults to exactOrRegexp</td></tr>
+    <tr><td>validate</td><td>true to force ivy files validation against ivy.xsd, false to force no validation</td>
+        <td>No. Defaults to default ivy value (as configured in configuration file)</td></tr>
+</tbody>
+</table>
+
+<h1>Examples</h1>
+To generate a xml report for all the latest versions of all the modules in your repository:
+<code type="xml">
+<ivy:repreport />
+</code>
+
+<hr/>
+To generate a graphml report for all the latest versions of all the modules in your repository:
+<code type="xml">
+<ivy:repreport xml="false" graph="true" />
+</code>
+
+<hr/>
+To generate a xml report for all the latest versions of the modules from the organisation foo in your repository:
+<code type="xml">
+<ivy:repreport organisation="foo" />
+</code>
+
+<hr/>
+To generate a xml report for all the versions on the 1.x stream of the modules named bar* from the organisation foo in your repository:
+<code type="xml">
+<ivy:repreport organisation="foo" module="bar*" revision="1.+" matcher="glob" />
+</code>
+
+<hr/>
+To generate an XML report using a custom stylesheet:
+<code type="xml">
+<ivy:repreport xsl="true" xslfile="my-custom-stylesheet.xsl" xslext="xml" />
+</code>
+
+<hr/>
+To generate an XML report using a custom stylesheet which needs some parameters:
+<code type="xml">
+<ivy:repreport xsl="true" xslfile="my-custom-stylesheet.xsl" xslext="xml">
+    <param name="param1" expression="value1" /> 
+    <param name="param2" expression="value2" /> 
+</report>
+</code>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>



Mime
View raw message