You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by xa...@apache.org on 2007/07/04 15:41:57 UTC

svn commit: r553243 [2/8] - in /incubator/ivy/core/trunk/doc: ./ configuration/ configuration/macrodef/ configuration/namespace/ doc/ history/ ivyfile/ presentations/ resolver/ schemas/ test/ tutorial/ tutorial/build-repository/ use/

Added: incubator/ivy/core/trunk/doc/configuration/macrodef/attribute.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/macrodef/attribute.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/macrodef/attribute.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/macrodef/attribute.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,48 @@
+<!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">
+<b>Tag:</b> attribute
+
+Defines a macrodef attribute. See macrodef for details.
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>name</td><td>the name of the attribute</td>
+        <td>Yes</td></tr>
+    <tr><td>default</td><td>the default value of the attribute if none is specified</td>
+        <td>No, by default attribute are required</td></tr>
+</tbody>
+</table>
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/macrodef/attribute.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/module.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/module.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/module.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/module.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,102 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> module
+
+Define a module set rule. The tag defines a module set, by giving an expression and the matcher to use for organisation and name (for instance, you can use * to specify all). 
+
+It also gives the specific setting to use for this module set.
+
+For each module set, you can configure:
+<ul>
+<li>the <a href="../../doc/configuration/resolvers.html">resolver</a> to use</li>
+<li>the <a href="../../doc/configuration/conflict-managers.html">conflict manager</a> to use</li>
+<li>the default <a href="../../doc/terminology#branch.html">branch</a> to use</li>
+</ul>
+
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>organisation</td><td>the name of the organisation to which apply the resolver. May be an expression depending on the matcher used (see matcher attribute below).</td>
+        <td>Yes</td></tr>
+    <tr><td>name</td><td>the name of the module to which apply the resolver. May be an expression depending on the matcher used (see matcher attribute below).</td>
+        <td>Yes</td></tr>
+    <tr><td>matcher</td><td>the <a href="../concept.html#matcher">matcher</a> to use to match the modules to which the resolver should be applied <span class="since">since 1.3</span></td>
+        <td>No, defaults to exactOrRegexp</td></tr>
+    <tr><td>resolver</td><td>the name of the resolver to apply. The resolver must have been defined in the resolvers section of the configuration file.</td>
+        <td>No</td></tr>
+    <tr><td>conflict-manager</td><td>the name of the conflict manager to apply. <span class="since">since 1.4</span></td>
+        <td>No</td></tr>
+    <tr><td>branch</td><td>the default branch to apply. <span class="since">since 1.4</span></td>
+        <td>No</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<modules>
+  <module organisation="jayasoft" name="*" resolver="myprojectsresolver"/>
+</modules>
+</code>
+Uses myprojectresolver for all modules from jayasoft.
+<hr/>
+<code type="xml">
+<modules>
+  <module organisation="apache" name="commons-*" matcher="glob" resolver="myapachecommonsresolver"/>
+</modules>
+</code>
+Uses myapachecommonsresolver for all modules beginning by commons- from apache.
+<hr/>
+<code type="xml">
+<modules>
+  <module organisation="apache" name="commons-[a-z]+" matcher="regexp" resolver="myapachecommonsresolver"/>
+</modules>
+</code>
+Uses myapachecommonsresolver for all modules from apache beginning by commons- followed by any number of alphabetic lowercase characters.
+<hr/>
+<code type="xml">
+<modules>
+  <module organisation="apache" name="ivy*" matcher="glob" conflict-manager="latest-time"/> 
+</modules>
+</code>
+Uses latest-time conflict manager for all modules from apache which name begins with ivy.
+<hr/>
+<code type="xml">
+<modules>
+  <module organisation="apache" name="ivy*" matcher="glob" branch="fix-103"/> 
+</modules>
+</code>
+Uses 'fix-103' as default branch for all modules from apache which name begins with ivy.
+
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/module.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/modules.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/modules.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/modules.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/modules.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,52 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> modules
+
+Defines per module or module set settings.
+
+The rules are given by defining a module set, using pattern for module organisation and name, and giving some settings for the set, like the name of the corresponding resolver to use.
+
+If no rule match a given module, the default setting will be used.
+
+Even if not required, because the use of a default big resolver (chain, for instance) able to resolve all dependencies can answer all the needs, the configuration of smaller resolvers used for different cases can improve performances a lot. For instance, if you have a local repository for your modules and a distant repository for third party libraries, it is a good idea to have two separate resolvers, and configure ivy to use one for all your modules and another for the rest (the default one).
+
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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="../../doc/configuration/module.html">module</a></td><td>defines a module set rule</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/modules.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/namespace.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/namespace.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/namespace.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/namespace.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,128 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> namespace
+
+Defines a new namespace. A namespace is identified by a name, which is used to reference the namespace in the resolvers using the namespace.
+
+Namespaces overview is given in the <a href="../../doc/configuration/namespaces.html">namespaces</a> documentation.
+
+A namespace mainly consists of a list of rules, each rule defining a translation between system namespace and the defined namespace, and vice versa.
+
+There are two main possibilities for using these rules. By default, a namespace iterate through the rules, and when it finds one that translate the given name, it returns the translated name. But the namespace can be configured to do use the list as a translator chain: in this case, all rules are applied in order, the result of the first rule translation being passed to the second, and so on.
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>name</td><td>the namespace name</td>
+        <td>Yes</td></tr>
+    <tr><td>chainrules</td><td>true to indicate that namespaces rules should be chained, false otherwise</td>
+        <td>No, defaults to false</td></tr>
+</tbody>
+</table>
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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="../../doc/configuration/namespace/rule.html">rule</a></td><td>defines a new namespace rule</td>
+        <td>0..n</td></tr>
+</tbody>
+</table>
+<h1>Example</h1>
+<code type="xml">
+<namespace name="test">
+  <rule>
+    <fromsystem>
+      <src org="systemorg"/>
+      <dest org="A"/>
+    </fromsystem>
+    <tosystem>
+      <src org="A"/>
+      <dest org="systemorg"/>
+    </tosystem>
+  </rule>
+</namespace>
+</code>
+
+<code type="xml">
+<namespace name="test">
+  <rule>
+    <fromsystem>
+      <src org="systemorg2" module="system\-(.+)"/>
+      <dest org="B" module="$m1"/>
+    </fromsystem>
+    <tosystem>
+      <src org="B" module=".+"/>
+      <dest org="systemorg2" module="system-$m0"/>
+    </tosystem>
+  </rule>
+</namespace>
+</code>
+
+<code type="xml">
+<namespace name="test" chainrules="true">
+  <rule>
+    <fromsystem>
+      <src org="systemorg"/>
+      <dest org="A"/>
+    </fromsystem>
+    <tosystem>
+      <src org="A"/>
+      <dest org="systemorg"/>
+    </tosystem>
+  </rule>
+  <rule>
+    <fromsystem>
+      <src module="systemmod"/>
+      <dest module="A"/>
+    </fromsystem>
+    <tosystem>
+      <src module="A"/>
+      <dest module="systemmod"/>
+    </tosystem>
+  </rule>
+  <rule>
+    <fromsystem>
+      <src module="systemmod2"/>
+      <dest module="B"/>
+    </fromsystem>
+    <tosystem>
+      <src module="B"/>
+      <dest module="systemmod2"/>
+    </tosystem>
+  </rule>
+</namespace>
+</code>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/namespace.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/namespace/dest.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/namespace/dest.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/namespace/dest.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/namespace/dest.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,63 @@
+<!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">
+<b>Tag:</b> dest
+
+Defines the translation part of a translation rule. If a name has matched a corresponding src, it will be translated using this dest part.
+
+The new names can contain references to groups of the matched name, using a slightly modified regexp syntax. Indeed, referenced groups can be part of either the organisation, module or revision part of the original name. So, to reference the groups, you just have to add a letter identifying the part in which the group should be selected: o for organisation, m for module, and r for revision.
+
+For instance, $o0 matches the whole matched organisation, and $m0 the whole matched module name. $o1 matches the first group of the matched organisation.
+
+For details about regexp and groups, see the <a href="http://java.sun.com/j2se/1.4.2/docs/api/java/util/regex/Pattern.html">Pattern class documentation</a> in the jdk.
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>org</td><td>the new organisation name</td>
+        <td>No, defaults to $o0</td></tr>
+    <tr><td>module</td><td>the new module name</td>
+        <td>No, defaults to $m0</td></tr>
+    <tr><td>rev</td><td>the new revision</td>
+        <td>No, defaults to $r0</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+    <fromsystem>
+      <src org="systemorg2" module="system\-(.+)"/>
+      <dest org="B" module="$m1"/>
+    </fromsystem>
+</code>
+Matches modules from systemorg2 which have a name beginning with system followed by a minus and anything else, and translate it to organisation B and module the part following <code>system-</code> of the original name.
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/namespace/dest.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/namespace/fromtosystem.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/namespace/fromtosystem.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/namespace/fromtosystem.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/namespace/fromtosystem.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,47 @@
+<!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">
+<b>Tag:</b> fromsystem / tosystem
+
+Defines a one way translation rule, i.e. a translation from system namespace to the defined namespace or vice versa.
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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="../../../doc/configuration/namespace/src.html">src</a></td><td>defines a source name which can be accepted</td>
+        <td>1..n</td></tr>
+    <tr><td><a href="../../../doc/configuration/namespace/dest.html">dest</a></td><td>defines the translation to apply when a name is accepted by an src pattern</td>
+        <td>1</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/namespace/fromtosystem.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/namespace/rule.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/namespace/rule.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/namespace/rule.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/namespace/rule.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,49 @@
+<!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">
+<b>Tag:</b> rule
+
+Defines a new namespace rule. A rule defines a translation between system namespace and the defined namespace, and vice versa.
+
+See <a href="../../../doc/configuration/namespace/namespace.html">namespace</a> doc for details.
+
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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="../../../doc/configuration/namespace/fromtosystem.html">fromsystem</a></td><td>defines the translation to apply from system namespace to the defined namespace</td>
+        <td>1</td></tr>
+    <tr><td><a href="../../../doc/configuration/namespace/fromtosystem.html">tosystem</a></td><td>defines the translation to apply from the defined namespace to system namespace</td>
+        <td>1</td></tr>
+</tbody>
+</table>
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/namespace/rule.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/namespace/src.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/namespace/src.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/namespace/src.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/namespace/src.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,49 @@
+<!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">
+<b>Tag:</b> src
+
+Defines the acceptation part of a translation rule. If a name matches this src, it will be translated using the dest part.
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>org</td><td>the organisation to match as a regexp</td>
+        <td>No, defaults to .*</td></tr>
+    <tr><td>module</td><td>the module name to match as a regexp</td>
+        <td>No, defaults to .*</td></tr>
+    <tr><td>rev</td><td>the revision to match as a regexp</td>
+        <td>No, defaults to .*</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/namespace/src.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/namespaces.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/namespaces.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/namespaces.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/namespaces.html Wed Jul  4 08:41:45 2007
@@ -0,0 +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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> namespaces
+
+Namespaces are an advanced feature of Ivy which let you use resolvers in which module names and organisations are not consistent between each other.
+
+For instance, if you want to use maven2 repository and ivyrep collectively, you will face some naming issues. For example all apache commons projects are declared to be part of the organisation apache in ivyrep whereas in maven2 ibiblio repository, they are declared to be part of the organisation of the same name of the module.
+
+So if you try to use both maven2 and ivyrep repositories, you will face some issues like:
+<quote>
+How do I declare a dependency on commons-lang ?
+I have an error while trying to resolve module xxx. It says that it depends on [commons-httpclient commons-httpclient] ant that it isn't available.
+...
+</quote>
+
+Ivy has an answer to give to this kind of troubles, and this answer is called namespaces. In short, you can affect a namespace to each dependency resolver in Ivy, and each namespace defines rules to convert names from the system namespace to the defined namespace itself, and vice versa.
+
+This very powerful feature is thoroughly used in the <a href="../../doc/tutorial/build-repository/advanced1.html">build your own repository tutorial</a>, and this is a good place to have examples of what can be done with namespaces.
+
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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="../../doc/configuration/namespace.html">namespace</a></td><td>defines a new namespace</td>
+        <td>0..n</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/namespaces.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/outputters.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/outputters.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/outputters.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/outputters.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,66 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> outputters
+
+Defines a list of report outputters usable in ivy. 
+
+A report outputter is used at the end of the resolve process to generate a report of how the resolve has been performed.
+
+Two report outputters are registered by default:
+<ul>
+<li>a log report outputter ([[svn:src/java/org/apache/ivy/report/LogReportOutputter.java LogReportOutputter]])</li>which produces the output on the console at the end of the resolve, which looks like this:
+<code>
+        ---------------------------------------------------------------------
+        |                  |            modules            ||   artifacts   |
+        |       conf       | number| search|dwnlded|evicted|| number|dwnlded|
+        ---------------------------------------------------------------------
+        |      default     |   1   |   1   |   0   |   0   ||   1   |   1   |
+        ---------------------------------------------------------------------
+</code>
+<li>an xml report outputter ([[svn:src/java/org/apache/ivy/report/XmlReportOutputter.java XmlReportOutputter]])</li>which produces an xml report in the cache, which is mandatory for correct Ivy behaviour, since it's that report which is used when you do a post resolve step in a separate buid from the resolve itself. It's also this xml report which is processed to generate all the different reports available in the [[ant:report]] task.
+</ul>
+
+The child tag used for the parser must be equal to a name of a report outputter type (added with the typedef tag).
+
+To see how to define your own report outputter see <a href="../../doc/extend.html">Extending Ivy documentation</a>
+
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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>any report outputter</td><td>adds a report outputter to the list of available ones</td>
+        <td>0..n</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/outputters.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/parsers.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/parsers.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/parsers.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/parsers.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,54 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> parsers
+
+Defines a list of module descriptor parsers usable in ivy. Each parser defines which resources (which descriptor file) it accepts.
+The child tag used for the parser must be equal to a name of a parser type (added with the typedef tag).
+
+Note that when looking for a parser, ivy queries the parsers list in the reverse order. So the last parser in the list will be queried first. Consequently, if the last parser accepts all resources, the other parsers will never have a chance to parse the resource.
+
+Two parsers are available by default and thus do not need to be declared in this section:
+<ul>
+<li>ivy file parser</li> this is the parser used for ivy xml files. This parser is used for resources that aren't accepted by any other parser.
+<li>pom parser</li>this parser is able to parse maven2 pom files
+</ul>
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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>any module descriptor parser</td><td>adds a module descriptor parser to the list of available parsers</td>
+        <td>0..n</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/parsers.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/properties.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/properties.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/properties.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/properties.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,48 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> properties<br/>
+<br/>
+Loads a properties file into ivy variables. See variables chapter above for details about ivy variables.
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>file</td><td>a path to a properties file to load</td>
+        <td>Yes</td></tr>
+    <tr><td>override</td><td>indicates if the variable found in the properties file should override their previous value, if any <span class="since">since 1.3</span></td>
+        <td>No, defaults to true</td></tr>
+</tbody>
+</table>
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/properties.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/property.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/property.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/property.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/property.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,62 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> property
+
+Defines an ivy variable. <span class="since">since 1.3</span>
+
+The optional override attribute enables to avoid overriding the previous value of the varable, which makes the definition behave like ant properties, which is particularly useful to define default values (values which are used only if they haven't been defined yet).
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>name</td><td>the name of the variable to define</td>
+        <td>Yes</td></tr>
+    <tr><td>value</td><td>the new value the variable must take</td>
+        <td>Yes</td></tr>
+    <tr><td>override</td><td>true if the previous value (if any) of the variable should overriden, false otherwise</td>
+        <td>No, defaults to true</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<property name="myvar" value="myvalue"/>
+</code>
+Sets the variable myvar to the value myvalue.
+<hr/>
+<code type="xml">
+<property name="myvar" value="myvalue" override="false"/>
+</code>
+Sets the variable myvar to the value myvalue only if myvar has not been set yet.
+
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/property.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/resolvers.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/resolvers.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/resolvers.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/resolvers.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,162 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> resolvers
+
+Defines a list of dependency resolvers usable in ivy. Each dependency resolver is identified by its name, given as an attribute.
+
+The child tag used for the dependency resolver must be equal to a name of a dependency resolver type (either built-in or added with the typedef tag).
+
+<span class="since">since 1.3</span> Once defined, resolvers can be referenced by their name, using the following syntax:
+<code type="xml">
+<resolver ref="alreadydefinedresolver"/>
+</code>
+Note that this works only if the resolver has been already defined, and not if it is defined later in the ivysettings file.
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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>any resolver</td><td>adds a resolver to the list of available resolvers</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+<h1>Built-in Resolvers</h1>
+Ivy comes with a set of built-in dependency resolvers able to answer to the most common needs. 
+
+If you don't find the one you want here, you can also check if some one has not contributed it in the <a href="../../links.html">links page</a>, or even <a href="../../doc/extend.html">write your own</a>.
+
+There are basically two types of resolver in Ivy: composite and standard resolvers. A composite resolver is a resolver which delegates the work to other resolvers. The other resolvers are standard resolvers.
+
+Here is the list of built-in resolvers:
+
+<table class="ivy-attributes">
+<thead>
+    <tr><th>Name</th><th>Type</th><th>Description</th></tr>
+</thead>
+<tbody>
+<tr><td><a href="../../doc/resolver/ivyrep.html">IvyRep</a></td><td>Standard</td><td>Finds ivy files on ivyrep and artifacts on ibiblio.</td></tr>
+<tr><td><a href="../../doc/resolver/ibiblio.html">IBiblio</a></td><td>Standard</td><td>Finds artifacts on ibiblio.</td></tr>
+<tr><td><a href="../../doc/resolver/filesystem.html">FileSystem</a></td><td>Standard</td><td>This very performant resolver finds ivy files and artifacts in your file system.</td></tr>
+<tr><td><a href="../../doc/resolver/url.html">Url</a></td><td>Standard</td><td>Finds ivy files and artifacts in any repository accessible with urls.</td></tr>
+<tr><td><a href="../../doc/resolver/vfs.html">Vfs</a></td><td>Standard</td><td>Finds ivy files and artifacts in any repository accessible with <a href="http://jakarta.apache.org/commons/vfs/">apache commons vfs</a>.</td></tr>
+<tr><td><a href="../../doc/resolver/ssh.html">ssh</a></td><td>Standard</td><td>Finds ivy files and artifacts in any repository accessible with ssh.</td></tr>
+<tr><td><a href="../../doc/resolver/sftp.html">sftp</a></td><td>Standard</td><td>Finds ivy files and artifacts in any repository accessible with sftp.</td></tr>
+<tr><td><a href="../../doc/resolver/chain.html">Chain</a></td><td>Composite</td><td>Delegates the finding to a chain of sub resolvers.</td></tr>
+<tr><td><a href="../../doc/resolver/dual.html">Dual</a></td><td>Composite</td><td>Delegates the finding of ivy files to one resolver and of artifacts to another.</td></tr>
+</tbody>
+</table>
+
+<h1><a name="common">Common attributes</a></h1>
+All resolvers of the same type share some common attributes detailed here:
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th><th>Composite</th><th>Standard</th></tr>
+</thead>
+<tbody>
+    <tr><td>name</td><td>the name which identify the resolver</td>
+        <td>Yes</td>
+        <td>Yes</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>validate</td><td>indicates if resolved ivy files should be validated against ivy xsd</td>
+        <td>No, defaults to call setting</td>
+        <td>Yes</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>checkmodified</td><td>Indicates if this resolver should check lastmodified date to know if an ivy file is up to date.</td>
+        <td>No, defaults to ${ivy.resolver.default.check.modified}</td>
+        <td>No</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>changingPattern</td><td>Indicates for which revision pattern this resolver should check lastmodified date to know if an artifact file is up to date. <span class="since">since 1.4</span></td>
+        <td>No, defaults to none</td>
+        <td>Yes</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>changingMatcher</td><td>The name of the <a href="../../doc/concept#matcher.html">pattern matcher</a> to use to match a revision against the configured changingPattern. <span class="since">since 1.4</span></td>
+        <td>No, defaults to exactOrRegexp</td>
+        <td>Yes</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>alwaysCheckExactRevision</td><td>Indicates if this resolver should check the given revision even if it's a special one (like latest.integration). <span class="since">since 1.3</span></td>
+        <td>No, defaults to ${ivy.default.always.check.exact.revision}</td>
+        <td>No</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>namespace</td><td>The name of the namespace to which this resolver belong <span class="since">since 1.3</span></td>
+        <td>No, defaults to 'system'</td>
+        <td>Yes</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>checkconsistency</td><td>true to check consistency of module descriptors found by this resolver, false to avoid consistency check <span class="since">since 1.3</span></td>
+        <td>No, defaults to true</td>
+        <td>No</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>allownomd</td><td>true if the absence of module descriptor (usually an ivy file) is authorised for this resolver, false to refuse modules without module descriptor <span class="since">since 1.4</span></td>
+        <td>No, defaults to true</td>
+        <td>No (except dual)</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>checksums</td><td>a comma separated list of <a href="../../doc/concept#checksum.html">checksum algorithms</a> to use both for publication and checking <span class="since">since 1.4</span></td>
+        <td>No, defaults to ${ivy.checksums}</td>
+        <td>No</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>latest</td><td>The name of the latest strategy to use.</td>
+        <td>No, defaults to 'default'</td>
+        <td>Yes</td>
+        <td>Yes</td>
+    </tr>
+</tbody>
+</table>
+
+<h1>Examples</h1>
+<code type="xml">
+<resolvers>
+  <filesystem name="1">
+    <ivy pattern="${ivy.settings.dir}/1/[organisation]/[module]/ivys/ivy-[revision].xml"/>
+    <artifact pattern="${ivy.settings.dir}/1/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/>
+  </filesystem>
+  <chain name="chain1">
+    <resolver ref="1"/>
+    <ivyrep name="ivyrep"/>
+  </chain>
+  <chain name="chain2" returnFirst="true" dual="true">
+    <resolver ref="1"/>
+    <ibiblio name="ibiblio"/>
+  </chain>
+</resolvers>
+</code>
+Defines a filesystem resolver, named '1', which is then used in two chains, the first which seconds the filesystem resolver with an ivyrep resolver, and second which seconds the filesystem resolver with an ibiblio resolver, and which returns the first module found, and uses the whole chain to download artifacts (see corresponding resolvers documentation for details about them).
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/resolvers.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/status.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/status.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/status.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/status.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,49 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> status
+
+Define one available module status.
+
+See <a href="../../doc/configuration/statuses.html">statuses</a> page for details about how statuses are defined.
+
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>name</td><td>name of status defined</td>
+        <td>Yes</td></tr>
+    <tr><td>integration</td><td>true if this is an integration status, false otherwise</td>
+        <td>No, defaults to false</td></tr>
+</tbody>
+</table>
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/status.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/statuses.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/statuses.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/statuses.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/statuses.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,73 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> statuses
+
+Defines the list of available statuses. <span class="since">since 1.4</span>
+
+By default, ivy has 3 statuses: release, milestone and integration. By adding a statuses section to your ivysettings file, you define the statuses you want to use. Note that in this case if you still want to have ivy default statuses you will have to declare them.
+
+The integration property on each status is only used for recursive delivery, an integration dependency being delivered if the caller is not in integration state itself.
+
+The default status is the one used when none is defined in a module descriptor. If not specified, it defaults to the last defined status.
+
+The statuses order is important, the first is considered the more mature, the last the less mature. This is used to know if a status is compatible with a latest.<status> version matcher.
+
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>default</td><td>the name of the status to use when none is declared in an ivy file</td>
+        <td>No, defaults to the last status declared</td></tr>
+</tbody>
+</table>
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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="../../doc/configuration/status.html">status</a></td><td>defines a new status</td>
+        <td>0..n</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<statuses default="bronze">
+  <status name="gold" integration="false"/>
+  <status name="silver" integration="false"/>
+  <status name="bronze" integration="true"/>
+</statuses> 
+</code>
+Defines 3 statuses, gold, silver and bronze. The default status used when none is declared in an ivy file will be bronze. 
+It is also considered as an integration status, and thus doesn't trigger any recrusive delivery.
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/statuses.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/triggers.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/triggers.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/triggers.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/triggers.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,218 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> triggers
+<span class="since">since 1.4</span>
+
+Defines a list of triggers to activate on some Ivy events.
+
+A trigger is an action which is performed whenever a particular event occurs.
+Ivy supports two type of triggers out of the box: ant-call and ant-build. The first calls a target in the same build as the original one whenever a particular event occurs, the second call an ant build which may be in another ant build script.
+
+If you want to use a different trigger, you can <a href="../../doc/extend.html">implement your own</a>.
+
+The event available in Ivy are the following ones:
+<table class="ivy-children">
+<thead>
+    <tr><th>Name</th><th>Attributes</th><th>Description</th></tr>
+</thead>
+<tbody>
+    <tr><td>pre-resolve</td>
+        <td>
+          <ul>
+            <li>organisation</li>the organisation of the module for which the dependencies will be resolved
+            <li>module</li>the name of the module for which the dependencies will be resolved
+            <li>revision</li>the revision of the module for which the dependencies will be resolved
+            <li>conf</li>comma separated list of configurations which will be resolved
+          </ul>
+        </td>
+        <td>Fired before a module dependencies will be resolved</td>
+    </tr>
+    <tr><td>pre-resolve-dependency</td>
+        <td>
+          <ul>
+            <li>organisation</li>the organisation of the dependency resolved
+            <li>module</li>the name of the dependency resolved
+            <li>revision</li>the revision asked for the dependency
+            <li>resolver</li>the name of the resolver used to resolve the dependency
+          </ul>
+        </td>
+        <td>Fired before each dependency is resolved in a single resolve call</td>
+    </tr>
+    <tr><td>post-resolve-dependency</td>
+        <td>
+          <ul>
+            <li>organisation</li>the organisation of the dependency resolved
+            <li>module</li>the name of the dependency resolved
+            <li>revision</li>the revision of the dependency resolved, or the revision asked if the resolution was not successful
+            <li>resolved</li>true if the resolution was successful, false otherwise
+            <li>resolver</li>the name of the resolver used to resolve the dependency
+          </ul>
+        </td>
+        <td>Fired after each dependency resolved in a single resolve call</td>
+    </tr>
+    <tr><td>post-resolve</td>
+        <td>
+          <ul>
+            <li>organisation</li>the organisation of the module for which the dependencies have been resolved
+            <li>module</li>the name of the module for which the dependencies have been resolved
+            <li>revision</li>the revision of the module for which the dependencies have been resolved
+            <li>conf</li>comma separated list of configurations resolved
+          </ul>
+        </td>
+        <td>Fired after a module dependencies has been resolved</td>
+    </tr>
+    <tr><td>pre-download-artifact</td>
+        <td>
+          <ul>
+            <li>organisation</li>the organisation of the artifact which is about to be downloaded
+            <li>module</li>the name of the module of the artifact which is about to be downloaded
+            <li>revision</li>the revision of the the artifact which is about to be downloaded
+            <li>artifact</li>the name of the the artifact which is about to be downloaded
+            <li>type</li>the type of the the artifact which is about to be downloaded
+            <li>ext</li>the extension of the the artifact which is about to be downloaded
+            <li>resolver</li>the name of the resolver used to download the artifact
+            <li>origin</li>the origin location from which it will be downloaded
+            <li>local</li>true if it's a local artifact, false otherwise
+          </ul>
+        </td>
+        <td>Fired before an artifact is downloaded from a repository to the cache</td>
+    </tr>
+    <tr><td>post-download-artifact</td>
+        <td>
+          <ul>
+            <li>organisation</li>the organisation of the artifact which was just downloaded
+            <li>module</li>the name of the module of the artifact which was just downloaded
+            <li>revision</li>the revision of the the artifact which was just downloaded
+            <li>artifact</li>the name of the the artifact which was just downloaded
+            <li>type</li>the type of the the artifact which was just downloaded
+            <li>ext</li>the extension of the the artifact which was just downloaded
+            <li>resolver</li>the name of the resolver used to download the artifact
+            <li>origin</li>the origin location from which it was downloaded
+            <li>local</li>true if it's a local artifact, false otherwise
+            <li>size</li>the size in bytes of the downloaded artifact
+            <li>file</li>the file to which it has been downloaded
+          </ul>
+        </td>
+        <td>Fired after an artifact has been downloaded from a repository to the cache</td>
+    </tr>
+</tbody>
+</table>
+
+
+The child tag used for the dependency resolver must be equal to a name of a trigger type (either built-in or added with the typedef tag).
+
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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>any trigger</td><td>adds a trigger to the list of registered triggers</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+<h1>Built-in Triggers</h1>
+Ivy comes with two built-in triggers: 
+
+<table class="ivy-attributes">
+<thead>
+    <tr><th>Name</th><th>Description</th></tr>
+</thead>
+<tbody>
+<tr><td>ant-build<a href="../../doc/trigger/ant-build.html"></a></td><td>Triggers an ant build.</td></tr>
+<tr><td>ant-call<a href="../../doc/trigger/ant-call.html"></a></td><td>Calls a target in the current ant build.</td></tr>
+</tbody>
+</table>
+
+
+<h1><a name="common">Common attributes</a></h1>
+All triggers share some common attributes detailed here.
+
+Among these attributes, you will find how to select when the trigger should be performed. You have to provide an event name, which is simple, but you can also use a filter expression. The syntax for this expression is very simple and limited: 
+you can use the = operator to compare an attribute (left operande) with a value (right operande).
+you can use AND OR NOT as boolean operators
+you cannot use parenthesis to change the precedence
+
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>name</td><td>the name of the trigger for identification purpose only</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>event</td><td>the name of the event on which the trigger should be performed</td>
+        <td>Yes</td>
+    </tr>
+    <tr><td>filter</td><td>a filter expression used to restrict when the trigger should be performed</td>
+        <td>No, defaults to no filter</td>
+    </tr>
+</tbody>
+</table>
+
+<h1>Examples</h1>
+<code type="xml">
+<triggers>
+    <ant-build antfile="${ivy.settings.dir}/[module]/build.xml" target="publish"
+           event="pre-resolve-dependency" filter="revision=latest.integration"/>
+</triggers>
+</code>
+Triggers an ant build of the ant file ${ivy.settings.dir}/[module]/build.xml (where [module] is replaced by the name of the dependency resolved) with the target "publish", just before resolving a dependency with a latest.integration revision.
+<hr/>
+<code type="xml">
+<triggers>
+    <ant-call target="unzip" prefix="dep"
+          event="post-download-artifact" filter="type=zip AND status=successful"/>
+</triggers>
+</code>
+Triggers an ant call of the target unzip just after downloading a zip artifact, prefixing all parameters to the target with 'dep'.
+Here is how the target can look like:
+<code type="xml">
+<target name="unzip">
+     <echo>
+        unzipping artifact: 
+        organisation=${dep.organisation} 
+        module=${dep.module} 
+        revision=${dep.revision}
+        artifact=${dep.artifact}
+        type=${dep.type}
+        ext=${dep.ext}
+        origin=${dep.origin}
+        local=${dep.local}
+        size=${dep.size}
+        file=${dep.file}
+     </echo>
+     <mkdir dir="${basedir}/out"/>
+     <unzip src="${dep.file}" dest="${basedir}/out"/>
+</target>
+</code>
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/triggers.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/typedef.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/typedef.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/typedef.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/typedef.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,48 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> typedef<br/>
+<br/>
+Defines a new type in ivy. Useful to define new dependency resolvers, in particular, but also latest strategies.
+See <a href="../../doc/extend.html">how to write and plug your own dependency resolver</a> for details.
+<h1>Attributes</h1>
+<table class="ivy-attributes">
+<thead>
+    <tr><th class="ivy-att">Attribute</th><th class="ivy-att-desc">Description</th><th class="ivy-att-req">Required</th></tr>
+</thead>
+<tbody>
+    <tr><td>name</td><td>the name of the type to define. This name is then used as an xml tag.</td>
+        <td>Yes</td></tr>
+    <tr><td>classname</td><td>the fully qualified class name of the type to define.</td>
+        <td>Yes</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/typedef.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/configuration/version-matchers.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/configuration/version-matchers.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/configuration/version-matchers.html (added)
+++ incubator/ivy/core/trunk/doc/configuration/version-matchers.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,52 @@
+<!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: 1};</script>	
+	<script type="text/javascript" src="../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<b>Tag:</b> version-matchers
+
+Defines a list of version matchers. <span class="since">since 1.4</span> 
+
+The child tag used for the version matcher must be equal to a name of a report outputter type (added with the typedef tag).
+
+A version matcher is used to evaluate if a a dependency version contraint matches a dependency version.
+
+See <a href="../../doc/ivyfile/dependency.html">dependency</a> doc for details about built-in version matchers.
+
+<h1>Child elements</h1>
+<table class="ivy-children">
+<thead>
+    <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>any version matcher</td><td>adds a version matcher to the list of available ones</td>
+        <td>0..n</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/configuration/version-matchers.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/dev.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/dev.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/dev.html (added)
+++ incubator/ivy/core/trunk/doc/dev.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,176 @@
+<!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: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<h1>Building from source</h1>
+To build Ivy from source it's really easy. 
+<h2>Requirements</h2>
+All you need is 
+<ul>
+<li>an <a href="http://subversion.tigris.org/">svn</a> client</li>
+<em>to check out Ivy sources from apache svn, not required if you build from sources packaged in a release</em>
+<li><a href="http://ant.apache.org/">Apache Ant</a> 1.6.2 or greater</li>
+<em>We recommend either ant 1.6.5 or 1.7.0</em>
+<li><a href="http://junit.org">junit</a> 3.8.2 jar in your ant lib</li>
+<em> this is not required if you use ant 1.7</em>
+<li>a <a href="http://java.sun.com/">jdk</a> 1.4 or greater</li>
+<em>Build instructions have been successfully tested with sun jdk 1.4.2, 1.5.0 and 1.6.0</em>
+</ul>
+
+<h2>Procedure</h2>
+<h3>Get the source</h3>
+You can either get the sources from a [[download release]], or get them directly from svn. For instance, to get the trunk version:
+<code>
+svn co https://svn.apache.org/repos/asf/incubator/ivy/core/trunk ivy
+</code>
+<h3>Build</h3>
+Go to the directory where you get the Ivy sources (you should see a file named build.xml) and run:
+<code>
+ant
+</code>
+<h3>Check the result</h3>
+The ant build will download Ivy if you don't already have a proper version in your home, compile, and run tests with coverage metrics.
+If everything goes well, you should see the message
+<code>
+BUILD SUCCESSFUL
+</code>
+Then you can check the test results in the build/doc/reports/test directory, the jars are in build/artifacts, and the test coverage report in build/doc/reports/coverage
+<h1>Coding conventions</h1>
+The Ivy code base is supposed to follow the standard java conventions:
+http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html
+
+This is a work in progress though (see IVY-511), but patches helping migration to these conventions are welcome.
+
+<h1>Developing with eclipse</h1>
+Even though you can develop Ivy with your IDE of choice, we support eclipse development by providing ad hoc metadata.
+
+We currently provide two options:
+<h2>Eclipse alone</h2>
+To develop with a simple eclipse install all you need is eclipse 3.1 or greater, with no particular plugin.
+First call the following ant target in your Ivy workspace:
+<code>
+ant eclipse-default
+</code>
+This will resolve the dependencies of Ivy and produce a .classpath using the resolved jars for the build path.
+Then you can use the "Import->Existing project into workspace" eclipse feature to import the Ivy project in your workspace.
+<h2>Eclipse + IvyDE</h2>
+You can also leverage the latest IvyDE version to be able to easily resolve the ivy dependencies from Eclipse.
+To do so all you need is call the following ant target in your Ivy workspace:
+<code>
+ant eclipse-ivyde
+</code>
+or if you don't have ant installed you can simply copy the file .classpath.ivyde and rename it to .classpath
+Then you can import the project using "Import->Existing project into workspace" as long as you already have latest IvyDE installed.
+
+To install latest IvyDE version compatible with the latest Ivy used to resolve Ivy dependencies, you will need to use a snapshot build, not endorsed by the ASF, available here:
+http://people.apache.org/~xavier/ivyde/snapshot/
+
+Download the file and unzip its content in your eclipse installation directory.
+
+<h1>Making a release</h1>
+<h2>Requirements</h2>
+Requirements for making a release are similar to the requirements for building from source, except that sun jdk 1.6 and ant 1.7 are required.
+<h2>Procedure</h2>
+<h3>1. Check the files which needs to be updated for the release.</h3>
+On the trunk, check that files which require update for the release are up to date.
+This includes particularly:
+RELEASE_NOTES
+CHANGES
+README
+<h3>2. Create a release branch</h3>
+This will allow to work separately from other developers, in case you need any last modification.
+<code>
+svn copy https://svn.apache.org/repos/asf/incubator/ivy/core/trunk \
+           https://svn.apache.org/repos/asf/incubator/ivy/core/branches/2.0.0-alpha1 \
+      -m "Creating a release branch for 2.0.0-alpha1."
+</code>
+<h3>3. Check out the branch</h3>
+<code>
+svn co https://svn.apache.org/repos/asf/incubator/ivy/core/branches/2.0.0-alpha1 ivy-2.0.0-alpha1
+</code>
+<h3>4. Double check the files which need to be updated for the release.</h3>
+Check again that files have proper revision information.
+It's also time to update the documentation template files which will be used for doc generation to include the version information in the page title.
+For instance in
+<code>
+doc/homeTemplate.html
+doc/template.html
+doc/printTemplate.html
+</code>
+replace
+<code>
+<title>${title} | Ivy</title>
+</code>
+by
+<code>
+<title>${title} | Ivy 2.0.0-alpha1-incubating</title>
+</code>
+<h3>5. Commit your changes</h3>
+<code>
+svn ci -m "update templates for 2.0.0-alpha-1 release."
+</code>
+<h3>6. Check that you have no pending modifications</h3>
+<code>
+svn status
+</code>
+If your working copy is clean, you can launch the release script. If it isn't, make sure to clean it properly. Sometimes you may need to call ant clean-all if you have started to work with ant builds. If you are confused about your working copy state, delete it and check it out again.
+<h3>7. Launch the release script</h3>
+<code>
+ant -Dbuild.version=2.0.0-alpha1-incubating -Dstatus=milestone -f build-release.xml release
+</code>
+The status should be release only for final releases, and milestone for any other intermediate release.
+If anything is wrong, fix and go back to step 4.
+If the release script is successful, release artifacts will be waiting for you in the build/distrib directory.
+<h3>8. Verify the release</h3>
+Check that all zips can be opened correctly, and that running 'ant' after unzipping the source distribution works properly.
+You can also do a smoke test with the generated ivy.jar , to see if it is able to resolve properly a basic module (for instance you can replace the jar you have in your ~/.ivy/jars directory, clean your cache, and run 'ant clean jar'.
+<h3>9. Sign and upload the artifacts</h3>
+You will still need to sign the release artifacts and upload them to a location accessible by other Apache commiters
+<h3>10. Cast a vote to approve the release</h3>
+Cast a vote to approve the release, first on the ivy-dev mailing list, then if it is approved, on the general@incubator.apache.org mailing list
+<h3>11. Tag the svn repository</h3>
+Now that the release is approved, it is time to tag the svn repo
+<code>
+svn copy https://svn.apache.org/repos/asf/incubator/ivy/core/branches/2.0.0-alpha1 \
+           https://svn.apache.org/repos/asf/incubator/ivy/core/tags/2.0.0-alpha1 \
+      -m "Tag release 2.0.0-alpha1."
+</code>
+<h3>12. Upload to public repository</h3>
+If the release is approved, it's now time to make it public by uploading it to the public Apache distrib repository (i.e. /www/people.apache.org/dist/incubator/ivy/[version] on people.a.o).
+
+<h3>13. Announce</h3>
+Announce the release on the ivy-dev and ivy-user mailing lists, on the general@i.a.o list, announce@apache.org and on the user@ant.apache.org.
+Announce also the release on Ivy web site by editing the doc/index.html on the trunk.
+You can also announce the release on popular web sites, like freshmeat.net (xavier is the owner of the Ivy project on freshmeat), javalobby.org, theserverside.com, dzone.com, ...
+<h3>14. Update this doc</h3>
+If you feel like anything is missing or misleading in this release doc, update it as soon as you encounter the problem.
+<h3>15. Merge your modifications back to the trunk if necessary.</h3>
+Modifications on the template files do not need to be merged, but if you had troubles during your release you may want to merge your fixes back to the trunk.
+<h3>16. Prepare next release</h3>
+Update the file version.properties with the version of the next release so that anyone building from the trunk will obtain jar with the correct version number.</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/dev.html
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/ivy/core/trunk/doc/extend.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/extend.html?view=auto&rev=553243
==============================================================================
--- incubator/ivy/core/trunk/doc/extend.html (added)
+++ incubator/ivy/core/trunk/doc/extend.html Wed Jul  4 08:41:45 2007
@@ -0,0 +1,66 @@
+<!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: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Many things are configurable in ivy, and many things are available with ivy core. But when you want to do 
+something not built in ivy core, you can still plug your own code.<br/><br/>
+
+Several things are pluggable in ivy:
+<ul>
+<li>module descriptor parsers</li>
+<li>dependency resolvers</li>
+<li>latest strategies</li>
+<li>conflict managers</li>
+<li>report outputters</li>
+<li>version matchers</li>
+<li>triggers</li>
+</ul>
+
+Before trying to implement your own, we encourage you to check if the solution to your problem cannot be 
+addressed by existing features, or by <a href="../links.html">contributed ones</a>. Do not hesitate to ask for help on the [[mailing-lists]].<br/><br/>
+
+If you still don't find what you need, then you'll have to develop your own plugin or find someone who could do that for you.<br/><br/>
+
+Here are the main things to know if you want to develop your own plugins...<br/><br/>
+
+All ivy plug-ins use the same code patterns as ant specific tasks for parameters. This means that
+if you want to have a "myattribute" of type String, you just have to declare a method called
+setMyattribute(String val) on your plug-in. The same applies to child tags, you just have to follow ant specifications.<br/><br/>
+
+Knowing that, you then have to implement the appropriate interface:
+<ul>
+<li>org.apache.ivy.DependencyResolver for dependency resolvers</li>
+<li>org.apache.ivy.LatestStrategy for latest strategies</li>
+<li>org.apache.ivy.ConflictManager for conflict managers</li>
+<li>org.apache.ivy.parser.ModuleDescriptorParser for module descriptor parsers</li>
+</ul>
+
+To help you understand what is required in each implementation, and what you can use to do it, have a look to existing implementations, it's the best advice we can give you!
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/extend.html
------------------------------------------------------------------------------
    svn:eol-style = native