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/05 14:12:58 UTC
svn commit: r553512 [2/2] - in /incubator/ivy/core/trunk/doc: ./
configuration/ configuration/namespace/ ivyfile/ resolver/ tutorial/
tutorial/build-repository/ use/
Modified: incubator/ivy/core/trunk/doc/ivyfile/dependency.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/dependency.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/dependency.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/dependency.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> dependency <b>Parent:</b> <a href="../../doc/ivyfile/dependencies.html">dependencies</a>
+<b>Tag:</b> dependency <b>Parent:</b> <a href="../ivyfile/dependencies.html">dependencies</a>
Declares a dependency for this module. A dependency is described by the module on which the current module depends (identified by its name, organisation and revision), and a mapping of configurations.
@@ -35,7 +35,7 @@
<li>latest.integration</li> selects the latest revision of the dependency module.
<li>latest.[any status]</li> selects the latest revision of the dependency module with at least the specified status. <span class="since">since 1.4</span>
For instance latest.milestone will select the latest version being either a milestone or a release, and latest.release will only selects the latest release. Note that in order to find the latest revision with the appropriate status Ivy has to parse all the ivy files in your repository from the last one until it finds such a revision. Hence don't be surprised if the resolution slow down.
-See also [[doc/configuration/statuses]] to see how to configure module statuses.
+See also [[configuration/statuses]] to see how to configure module statuses.
<li>end the revision with a +</li> selects the latest sub-revision of the dependency module. For instance,
if the dependency module exists in revision 1.0.3, 1.0.7 and 1.1.2, "1.0.+" will select 1.0.7.
<li>version ranges</li> mathematical notation for ranges can be used to match a range of version. <span class="since">since 1.4</span>
@@ -49,8 +49,8 @@
(,2.0] matches all versions lower or equal to 2.0
(,2.0[ matches all versions lower than 2.0
</ul>
-<span class="since">since 1.4</span> If you don't find a way to expression your dependency version constraint among these, you can <a href="../../doc/configuration/version-matchers.html">plug your own</a>.
-The way to determine which revision is the "latest" between two is configurable through the use of pluggable LatestStrategy. See <a href="../../doc/reference.html">ivy main concepts</a> for details about this.
+<span class="since">since 1.4</span> If you don't find a way to expression your dependency version constraint among these, you can <a href="../configuration/version-matchers.html">plug your own</a>.
+The way to determine which revision is the "latest" between two is configurable through the use of pluggable LatestStrategy. See <a href="../reference.html">ivy main concepts</a> for details about this.
<h2>Configurations mapping</h2>
This mapping indicates which configurations of the dependency are required in which configurations of the current module, also called master configurations.
@@ -60,11 +60,11 @@
The first way to declare this mapping is called the inline mapping. It is maybe the less natural at first, but it's powerful and concise. Inline mapping can take several forms.
<ul>
-<li>Specify one configuration name</li> This means that in this master configuration the same dependency configuration is needed (except if a defaultconfmapping has been specified in this ivy file, see <a href="../../doc/ivyfile/configurations.html">configurations</a> for details, or table below for examples).
+<li>Specify one configuration name</li> This means that in this master configuration the same dependency configuration is needed (except if a defaultconfmapping has been specified in this ivy file, see <a href="../ivyfile/configurations.html">configurations</a> for details, or table below for examples).
For instance, if the current module has defined a configuration named 'runtime', and the dependency too, then having an inline mapping configuration set to 'runtime' means that in the runtime master configuration the runtime dependency configuration is required.
<a name="defaultconfmapping"/>More examples:
-The table below indicates how ivy interpret the conf attribute according to how <a href="../../doc/ivyfile/configurations.html">defaultconfmapping</a> is set:<table class="ivy-attributes"><thead><tr><th>defaultconfmapping</th><th>conf</th><th>ivy interpretation</th></tr>
+The table below indicates how ivy interpret the conf attribute according to how <a href="../ivyfile/configurations.html">defaultconfmapping</a> is set:<table class="ivy-attributes"><thead><tr><th>defaultconfmapping</th><th>conf</th><th>ivy interpretation</th></tr>
</thead>
<tbody>
<tr><td></td><td></td><td><code>*->*</code></td></tr>
@@ -120,9 +120,9 @@
<h2>Forcing revision</h2>
Finally, the dependency element also supports an a force attribute (since 0.8), which gives an indication
to conflicts manager to force the revision of a dependency to the one given here.<br/>
-See <a href="../../doc/ivyfile/conflicts.html">conflicts manager</a> for details. <br/><br/>
+See <a href="../ivyfile/conflicts.html">conflicts manager</a> for details. <br/><br/>
-<span class="since">since 1.4</span> this tag supports <a href="../../doc/concept#extra.html">extra attributes</a>
+<span class="since">since 1.4</span> this tag supports <a href="../concept#extra.html">extra attributes</a>
<h1>Attributes</h1>
<table class="ivy-attributes">
<thead>
@@ -134,11 +134,11 @@
<tr><td>name</td><td>the module name of the dependency</td>
<td>Yes</td></tr>
<tr><td>branch</td><td>the branch of the dependency. <span class="since">since 1.4</span></td>
- <td>No, defaults to the default branch <a href="../../doc/configuration/conf.html">configured</a> for the dependency.</td></tr>
+ <td>No, defaults to the default branch <a href="../configuration/conf.html">configured</a> for the dependency.</td></tr>
<tr><td>rev</td><td>the revision of the dependency. See <a href="#revision">above</a> for details.</td>
<td>Yes</td></tr>
<tr><td>force</td><td>a boolean to give an indication to conflict manager that this dependency
- should be forced to this revision (see <a href="../../doc/ivyfile/conflicts.html">conflicts manager</a>)</td>
+ should be forced to this revision (see <a href="../ivyfile/conflicts.html">conflicts manager</a>)</td>
<td>No, defaults to false</td></tr>
<tr><td>conf</td><td>an inline mapping configuration spec (see above for details)</td>
<td>No, defaults to defaultconf attribute of dependencies element if neither conf attribute nor conf children element is given</td></tr>
@@ -154,11 +154,11 @@
<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/ivyfile/dependency-conf.html">conf</a></td><td>defines configuration mapping has sub element</td>
+ <tr><td><a href="../ivyfile/dependency-conf.html">conf</a></td><td>defines configuration mapping has sub element</td>
<td>0..n</td></tr>
- <tr><td><a href="../../doc/ivyfile/dependency-artifact.html">artifact / include</a></td><td>defines artifacts inclusion - use only if you do not control dependency ivy file</td>
+ <tr><td><a href="../ivyfile/dependency-artifact.html">artifact / include</a></td><td>defines artifacts inclusion - use only if you do not control dependency ivy file</td>
<td>0..n</td></tr>
- <tr><td><a href="../../doc/ivyfile/artifact-exclude.html">exclude</a></td><td>defines artifacts exclusion - use only if you do not control dependency ivy file</td>
+ <tr><td><a href="../ivyfile/artifact-exclude.html">exclude</a></td><td>defines artifacts exclusion - use only if you do not control dependency ivy file</td>
<td>0..n</td></tr>
</tbody>
</table>
Modified: incubator/ivy/core/trunk/doc/ivyfile/description.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/description.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/description.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/description.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> description <b>Parent:</b> <a href="../../doc/ivyfile/info.html">info</a><br/>
+<b>Tag:</b> description <b>Parent:</b> <a href="../ivyfile/info.html">info</a><br/>
<br/>
Describes the current module. This tag is the only one which can contain free text,
including html. It is used to describe the module itself, usually in a single short phrase
Modified: incubator/ivy/core/trunk/doc/ivyfile/exclude.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/exclude.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/exclude.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/exclude.html Thu Jul 5 07:12:52 2007
@@ -25,12 +25,12 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> exclude <b>Parent:</b> <a href="../../doc/ivyfile/dependencies.html">dependencies</a>
+<b>Tag:</b> exclude <b>Parent:</b> <a href="../ivyfile/dependencies.html">dependencies</a>
<span class="since">since 2.0</span> This feature gives you more control on a dependency for which you do not control its ivy file.
It allows to exclude artifacts, modules or organizations from the list of dependencies for the whole module.
-It is very similar to the [[doc/ivyfile/artifact-exclude dependency exclude]] element, except that it applies to a whole module, which can be very useful when a lot of dependencies transitively bring a module you don't want.
+It is very similar to the [[ivyfile/artifact-exclude dependency exclude]] element, except that it applies to a whole module, which can be very useful when a lot of dependencies transitively bring a module you don't want.
<h1>Attributes</h1>
<table class="ivy-attributes">
Modified: incubator/ivy/core/trunk/doc/ivyfile/include.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/include.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/include.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/include.html Thu Jul 5 07:12:52 2007
@@ -25,11 +25,11 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> include <b>Parent:</b> <a href="../../doc/ivyfile/configurations.html">configurations</a>
+<b>Tag:</b> include <b>Parent:</b> <a href="../ivyfile/configurations.html">configurations</a>
Include configurations specified in another file. <span class="since">since 1.3</span>
-The included file should have a configurations tag as root tag, which follow the same specification as the <a href="../../doc/ivyfile/configurations.html">configurations</a> tag of the ivy file.
+The included file should have a configurations tag as root tag, which follow the same specification as the <a href="../ivyfile/configurations.html">configurations</a> tag of the ivy file.
This means that it can contain conf declarations, other file inclusion, and also a defaultconfmapping.
Modified: incubator/ivy/core/trunk/doc/ivyfile/info.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/info.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/info.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/info.html Thu Jul 5 07:12:52 2007
@@ -25,11 +25,11 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> info <b>Parent:</b> <a href="../../doc/ivyfile.html">ivy-module</a>
+<b>Tag:</b> info <b>Parent:</b> <a href="../ivyfile.html">ivy-module</a>
Gives information about the module this ivy file describe.
-<span class="since">since 1.4</span> This tag supports <a href="../../doc/concept#extra.html">extra attributes</a>.
+<span class="since">since 1.4</span> This tag supports <a href="../concept.html#extra">extra attributes</a>.
<h1>Attributes</h1>
<table class="ivy-attributes">
@@ -42,10 +42,10 @@
<tr><td>module</td><td>the name of the module described by this ivy file.</td>
<td>Yes</td></tr>
<tr><td>branch</td><td>the branch of this module. <span class="since">since 1.4</span></td>
- <td>No, defaults to the default branch <a href="../../doc/configuration/conf.html">configured</a>, or nothing if no default branch is configured</td></tr>
+ <td>No, defaults to the default branch <a href="../configuration/conf.html">configured</a>, or nothing if no default branch is configured</td></tr>
<tr><td>revision</td><td>the revision of this module.</td>
<td>Yes in repository ivy files, no in ivy files to resolve</td></tr>
- <tr><td>status</td><td>the status of this module. See <a href="../../doc/reference.html">terminology</a> section for details</td>
+ <tr><td>status</td><td>the status of this module. See <a href="../reference.html">terminology</a> section for details</td>
<td>No, default to 'integration'</td></tr>
<tr><td>publication</td><td>the date of publication of this module. It should be given in this format: yyyyMMddHHmmss</td>
<td>No, but it's a good practice to set it with delivered ivy files</td></tr>
@@ -57,13 +57,13 @@
<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/ivyfile/license.html">license</a></td><td>contains information about the licenses of the described module</td>
+ <tr><td><a href="../ivyfile/license.html">license</a></td><td>contains information about the licenses of the described module</td>
<td>0..n</td></tr>
- <tr><td><a href="../../doc/ivyfile/ivyauthor.html">ivyauthor</a></td><td>describes who has contributed to write the ivy file</td>
+ <tr><td><a href="../ivyfile/ivyauthor.html">ivyauthor</a></td><td>describes who has contributed to write the ivy file</td>
<td>0..n</td></tr>
- <tr><td><a href="../../doc/ivyfile/repository.html">repository</a></td><td>describes on which public repositories this module can be found</td>
+ <tr><td><a href="../ivyfile/repository.html">repository</a></td><td>describes on which public repositories this module can be found</td>
<td>0..n</td></tr>
- <tr><td><a href="../../doc/ivyfile/.html">description</a></td><td>describes how to use the module</td>
+ <tr><td><a href="../ivyfile/.html">description</a></td><td>describes how to use the module</td>
<td>0..1</td></tr>
</tbody>
</table>
Modified: incubator/ivy/core/trunk/doc/ivyfile/ivyauthor.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/ivyauthor.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/ivyauthor.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/ivyauthor.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> ivyauthor <b>Parent:</b> <a href="../../doc/ivyfile/info.html">info</a><br/>
+<b>Tag:</b> ivyauthor <b>Parent:</b> <a href="../ivyfile/info.html">info</a><br/>
<br/>
Gives information about who has contributed to write this ivy file. It does NOT indicate who
is the author of the module itself.
Modified: incubator/ivy/core/trunk/doc/ivyfile/license.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/license.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/license.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/license.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> license <b>Parent:</b> <a href="../../doc/ivyfile/info.html">info</a><br/>
+<b>Tag:</b> license <b>Parent:</b> <a href="../ivyfile/info.html">info</a><br/>
<br/>
Gives information about a license of the described module.
<h1>Attributes</h1>
Modified: incubator/ivy/core/trunk/doc/ivyfile/manager.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/manager.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/manager.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/manager.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> manager <b>Parent:</b> <a href="../../doc/ivyfile/conflicts.html">conflicts</a><br/>
+<b>Tag:</b> manager <b>Parent:</b> <a href="../ivyfile/conflicts.html">conflicts</a><br/>
<br/>
Specify a a conflict manager for one or several dependencies.<br/>
The way to specify a conflict manager is by giving indication to which dependencies
@@ -33,7 +33,7 @@
and then specifying the conflict manager, either by giving its name or by
specifying a fixed revision list, in which case a fixed conflicts manager is used.<br/><br/>
-See <a href="../../doc/ivyfile/conflicts.html">Conflicts Manager</a> for details on conflicts manager in general.
+See <a href="../ivyfile/conflicts.html">Conflicts Manager</a> for details on conflicts manager in general.
<h1>Attributes</h1>
<table class="ivy-attributes">
Modified: incubator/ivy/core/trunk/doc/ivyfile/mapped.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/mapped.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/mapped.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/mapped.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> mapped <b>Parent:</b> <a href="../../doc/ivyfile/dependency-conf.html">conf</a><br/>
+<b>Tag:</b> mapped <b>Parent:</b> <a href="../ivyfile/dependency-conf.html">conf</a><br/>
<br/>
Describes a mapped dependency configuration for a master configuration.
Modified: incubator/ivy/core/trunk/doc/ivyfile/publications.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/publications.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/publications.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/publications.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> publications <b>Parent:</b> <a href="../../doc/ivyfile.html">ivy-module</a><br/><br/>
+<b>Tag:</b> publications <b>Parent:</b> <a href="../ivyfile.html">ivy-module</a><br/><br/>
Container for artifact elements, used to describe the artifacts published by this module.
If this container is not present, it is assumed that the module has one artifact, with the same name
Modified: incubator/ivy/core/trunk/doc/ivyfile/repository.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/ivyfile/repository.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/ivyfile/repository.html (original)
+++ incubator/ivy/core/trunk/doc/ivyfile/repository.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-<b>Tag:</b> repository <b>Parent:</b> <a href="../../doc/ivyfile/info.html">info</a><br/>
+<b>Tag:</b> repository <b>Parent:</b> <a href="../ivyfile/info.html">info</a><br/>
<br/>
Gives information about a public repository where the module can be found. This information
is given as an indication, repositories being able to be down over time.
Modified: incubator/ivy/core/trunk/doc/moreexamples.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/moreexamples.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/moreexamples.html (original)
+++ incubator/ivy/core/trunk/doc/moreexamples.html Thu Jul 5 07:12:52 2007
@@ -41,7 +41,7 @@
<h3><a href="http://www.opensymphony.com/webwork/">Webwork</a></h3>
The webwork project (which should become struts action framework) uses ant+ivy for their build, and thus make their framework very easy to use in an ant+ivy build system. They have a <a href="http://wiki.opensymphony.com/display/WW/Dependencies">page documenting how to use ivy with their framework</a>, which can be an interesting reading even if you don't plan to use webwork.
-<h3><a href="../doc/articles/ease-multi-module.html">Easing multi module development</a></h3>
+<h3><a href="articles/ease-multi-module.html">Easing multi module development</a></h3>
Johan stuyts, the author of SAnt, also contributed a nice article on his view of how to use Ivy on a multi module environment.
</textarea>
Modified: incubator/ivy/core/trunk/doc/principle.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/principle.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/principle.html (original)
+++ incubator/ivy/core/trunk/doc/principle.html Thu Jul 5 07:12:52 2007
@@ -29,7 +29,7 @@
<h1>Usual cycle of modules between different locations</h1>
<center><img src="../images/main-tasks.png" /></center>
-More details on ant tasks <a href="../doc/use/ant.html">here</a>.
+More details on ant tasks <a href="use/ant.html">here</a>.
<h1>Configure</h1>
Ivy needs to be configured to be able to resolve your dependencies. This configuration is usually done with a configuration file, which defines a set of dependency resolvers. Each resolver is able to find ivy files and / or artifacts, given simple information such as organition, module, revision, artifact name, artifact type and artifact extension.
Modified: incubator/ivy/core/trunk/doc/resolver/chain.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/chain.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/chain.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/chain.html Thu Jul 5 07:12:52 2007
@@ -33,7 +33,7 @@
This resolver is only a container of a chain of other resolvers. The sub resolvers can be any resolver, including a chain. An attribute enable to indicate if the chain must be iterated after the first found or not (at least when asking for a latest revision). If the chain is iterated, then it's the latest among the ones found that is returned. If the chain is not iterated, then it's the first found which is returned.
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of composite resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of composite resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/dual.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/dual.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/dual.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/dual.html Thu Jul 5 07:12:52 2007
@@ -34,7 +34,7 @@
This resolver delegates its job to one resolver for ivy files and another for artifacts.
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of composite resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of composite resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/filesystem.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/filesystem.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/filesystem.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/filesystem.html Thu Jul 5 07:12:52 2007
@@ -38,7 +38,7 @@
<span class="since">since 1.3</span> Using the m2compatible attribute, this resolver will convert dots found in organisation in slashes like maven2 does for groupId. For instance, it will transform the organisation from 'com.company' into 'com/company' when replacing the token [organisation] in your pattern.
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of standard resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/ibiblio.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/ibiblio.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/ibiblio.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/ibiblio.html Thu Jul 5 07:12:52 2007
@@ -45,7 +45,7 @@
</code>
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of standard resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/ivyrep.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/ivyrep.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/ivyrep.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/ivyrep.html Thu Jul 5 07:12:52 2007
@@ -35,7 +35,7 @@
<i>Note that if no ivy file is found on ivyrep, then this resolver behaves like ibiblio resolver. Thus it's usually better to use this resolver instead of ibiblio one, which is provided mainly for compatibility reasons.</i>
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of standard resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/sftp.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/sftp.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/sftp.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/sftp.html Thu Jul 5 07:12:52 2007
@@ -34,7 +34,7 @@
<br/>
This resolver can be used when your ivy repository is located on a server accessible via sftp. The secured nature of sftp and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
-If your server supports ssh but not sftp, there is also an <a href="../../doc/resolver/ssh.html">ssh resolver</a>.
+If your server supports ssh but not sftp, there is also an <a href="../resolver/ssh.html">ssh resolver</a>.
Note that sftp is also supported by vfs, so you can use a vfs resolver instead. The advantage of this resolver is that you have a better control over authentication, it can prompt for username/password credentials, or you can use private/public key authentication, which is not possible with the vfs resolver. When it prompts for username/password, it uses a Swing dialog, which is not possible in a headless environment. If you want to prompt for the credentials on the command line, use ant input task for example before calling ivy.
@@ -50,7 +50,7 @@
Internally this resolver relies on <a href="http://www.jcraft.com/jsch/">jsch</a> as ssh client, which is a popular java ssh client, used for example in eclipse.
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of standard resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/ssh.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/ssh.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/ssh.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/ssh.html Thu Jul 5 07:12:52 2007
@@ -34,11 +34,11 @@
<br/>
This resolver can be used when your ivy repository is located on a server accessible via ssh. The secured nature of ssh and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
-If your server supports sftp, you can consider using the <a href="../../doc/resolver/sftp.html">sftp resolver</a>.
+If your server supports sftp, you can consider using the <a href="../resolver/sftp.html">sftp resolver</a>.
-Internally this resolver shares most of its behaviour with the <a href="../../doc/resolver/sftp.html">sftp resolver</a>, so refer to its documentation for details.
+Internally this resolver shares most of its behaviour with the <a href="../resolver/sftp.html">sftp resolver</a>, so refer to its documentation for details.
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of standard resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/url.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/url.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/url.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/url.html Thu Jul 5 07:12:52 2007
@@ -35,7 +35,7 @@
This resolver is one of the most generic, in fact most of the previous resolvers can be obtained by a particular configuration of this one. Indeed it uses urls to find ivy files and artifacts. The urls it uses are defined through ivy and artifact children, each giving a pattern to find ivy files or artifacts.
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of standard resolvers.
<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>
Modified: incubator/ivy/core/trunk/doc/resolver/vfs.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/resolver/vfs.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/resolver/vfs.html (original)
+++ incubator/ivy/core/trunk/doc/resolver/vfs.html Thu Jul 5 07:12:52 2007
@@ -36,7 +36,7 @@
<i>Note: commons vfs has not released a stable version yet, hence Ivy relies on a nightly build. Stability should thus be considered carefully before using this resolver in a production environment</i>
<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+This resolver shares the <a href="../configuration/resolvers#common.html">common attributes</a> of standard resolvers.
<h1>Child elements</h1>
<table class="ivy-children">
<thead>
Modified: incubator/ivy/core/trunk/doc/terminology.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/terminology.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/terminology.html (original)
+++ incubator/ivy/core/trunk/doc/terminology.html Thu Jul 5 07:12:52 2007
@@ -60,7 +60,7 @@
and some others at runtime. All those differents ways to use or build a module
are called in ivy configurations.
-For more details on configurations and how they are used in ivy, please refer to the <a href="../doc/concept.html">main concepts page</a>.
+For more details on configurations and how they are used in ivy, please refer to the <a href="concept.html">main concepts page</a>.
<h2>Status</h2>
A module status indicates how stable a module revision can be considered. It can
be used to consolidate the status of all the dependencies of a module, to prevent
@@ -71,10 +71,10 @@
<li>milestone: revisions delivered to the public but not actually finished fall in this category</li>
<li>release: revision fully tested and labelled fall in this category</li>
</ul>
-<span class="since">since 1.4</span> This list is <a href="../doc/configuration/statuses.html">configurable</a> in your configuration file.
+<span class="since">since 1.4</span> This list is <a href="configuration/statuses.html">configurable</a> in your configuration file.
<h2>Repository</h2>
What is called a repository in Ivy is a location where Ivy is able to find your modules artifacts and metadata (i.e. ivy files in most cases).
-Ivy can be used with complex repositories configured very finely. You can use <a href="../doc/concept.html">Dependency Resolvers</a> to do so.
+Ivy can be used with complex repositories configured very finely. You can use <a href="concept.html">Dependency Resolvers</a> to do so.
</textarea>
<script type="text/javascript">xooki.postProcess();</script>
</body>
Modified: incubator/ivy/core/trunk/doc/tutorial/build-repository.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/tutorial/build-repository.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/tutorial/build-repository.html (original)
+++ incubator/ivy/core/trunk/doc/tutorial/build-repository.html Thu Jul 5 07:12:52 2007
@@ -25,10 +25,10 @@
</head>
<body>
<textarea id="xooki-source">
-With the <a href="../../doc/use/install.html">install</a> ant task you are given the possibility to copy ivy descriptors and artifacts found from a resolver and publish them into another resolver.<br/>
+With the <a href="../use/install.html">install</a> ant task you are given the possibility to copy ivy descriptors and artifacts found from a resolver and publish them into another resolver.<br/>
This tutorial will show you how to build your own clean enterprise repository of ivy descriptors and modules artifacts.
-We will first use some basic ivy settings files to show how it works, and then we will use advanced features like <a href="../../doc/configuration/namespaces.html">namespaces</a> to build a real enterprise repository.
+We will first use some basic ivy settings files to show how it works, and then we will use advanced features like <a href="../configuration/namespaces.html">namespaces</a> to build a real enterprise repository.
<h1>The project used</h1>
The project that we will use is quite simple.
Modified: incubator/ivy/core/trunk/doc/tutorial/build-repository/basic.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/tutorial/build-repository/basic.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/tutorial/build-repository/basic.html (original)
+++ incubator/ivy/core/trunk/doc/tutorial/build-repository/basic.html Thu Jul 5 07:12:52 2007
@@ -61,7 +61,7 @@
<ivy:install settingsRef="basic.settings" organisation="apache" module="commons-lang" revision="1.0" from="${from-resolver}" to="${to-resolver}" />
</target>
</code>
-After a declaration of the basic.settings, that make the ivy initialization with the right ivysettings file, we only call the task <a href="../../../doc/use/install.html">install</a> to retrieve apache commons-lang in it's 1.0 version.
+After a declaration of the basic.settings, that make the ivy initialization with the right ivysettings file, we only call the task <a href="../../use/install.html">install</a> to retrieve apache commons-lang in it's 1.0 version.
Here is the ant call output :
<div class="shell"><pre>Z:\ivy-repository>ant basic
Buildfile: build.xml
@@ -161,7 +161,7 @@
We can see here that <a href="/ivy">ivy</a> has resolved hibernate 2.1.8 and 24 depending modules. If we look at the ivy file for <a href="http://ivyrep.jayasoft.org/hibernate/hibernate/ivy-2.1.8.xml">hibernate 2.1.8</a>, we can see that it defines 17 dependencies. The 7 others that ivy retrieved, were transitive ones used in direct dependent modules of hibernate.
-We can notice that we have retrieve 3 different revisions of apache commons-logging (1.0.2, 1.0.3, 1.0.4) and 2 revisions of commons-collections (1.2, 1.2.1). This is due to the fact that we use the "no conflict" <a href="../../../doc/configuration/conflict-managers.html">conflic manager</a> in the ivysettings file.
+We can notice that we have retrieve 3 different revisions of apache commons-logging (1.0.2, 1.0.3, 1.0.4) and 2 revisions of commons-collections (1.2, 1.2.1). This is due to the fact that we use the "no conflict" <a href="../../configuration/conflict-managers.html">conflic manager</a> in the ivysettings file.
We do not want to evict any modules because we are building our own repository !
8 modules artifacts have not been downloaded cause they have not been found on ibiblio with the ivysettings as it is.
Modified: incubator/ivy/core/trunk/doc/tutorial/conf.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/tutorial/conf.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/tutorial/conf.html (original)
+++ incubator/ivy/core/trunk/doc/tutorial/conf.html Thu Jul 5 07:12:52 2007
@@ -29,7 +29,7 @@
More seriously, configurations in ivy can be better understood as views on your module, and you will see how they can be used efficiently here.
-Reference documentation on configurations can be found <a href="../../doc/terminology.html">here</a> and <a href="../../doc/ivyfile/configurations.html">here</a>.
+Reference documentation on configurations can be found <a href="../terminology.html">here</a> and <a href="../ivyfile/configurations.html">here</a>.
<h1>Introduction</h1>
Source code available in src/example/configurations/multi-projects.
We have two projects :
@@ -172,7 +172,7 @@
We also defined a dependency on the previous library.
In the dependency we use configuration mapping to match ours and library configurations.
-You can found more information on configuration mapping <a href="../../doc/ivyfile/configurations.html">here</a>
+You can found more information on configuration mapping <a href="../ivyfile/configurations.html">here</a>
<ol>
<li><b>build->api</b> : here we tell ivy that our <b>build</b> configuration depends on the api configuration of the dependcy</li>
<li><b>noexternaljar->homemade-impl</b> : here we tell ivy that our <b>noexternaljar</b> configuration depends on the <b>homemade-impl</b> configuration of the dependcy.</li>
Modified: incubator/ivy/core/trunk/doc/tutorial/defaultconf.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/tutorial/defaultconf.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/tutorial/defaultconf.html (original)
+++ incubator/ivy/core/trunk/doc/tutorial/defaultconf.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-Until Ivy 1.2a, the default resolver was a simple ivyrep resolver, with only a small number of possibilities of configuration. Whenever you wanted to do something slightly more complicated than looking for ivy files on ivyrep and artifacts on ibiblio, you had to write your own ivysettings file (see other tutorials and <a href="../../doc/configuration.html">settings</a> reference for details about this).
+Until Ivy 1.2a, the default resolver was a simple ivyrep resolver, with only a small number of possibilities of configuration. Whenever you wanted to do something slightly more complicated than looking for ivy files on ivyrep and artifacts on ibiblio, you had to write your own ivysettings file (see other tutorials and <a href="../configuration.html">settings</a> reference for details about this).
Ivy 1.3 introduced new default settings a lot more flexible.
@@ -205,7 +205,7 @@
</ivysettings>
</code>
-Here you are, you have enough clues to configure that the way you want... check the <a href="../../doc/configuration.html">settings documentation</a> to see if what you want to do is possible, and go ahead !
+Here you are, you have enough clues to configure that the way you want... check the <a href="../configuration.html">settings documentation</a> to see if what you want to do is possible, and go ahead !
</textarea>
<script type="text/javascript">xooki.postProcess();</script>
</body>
Modified: incubator/ivy/core/trunk/doc/tutorial/multi-project.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/tutorial/multi-project.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/tutorial/multi-project.html (original)
+++ incubator/ivy/core/trunk/doc/tutorial/multi-project.html Thu Jul 5 07:12:52 2007
@@ -55,7 +55,7 @@
</ivy-module>
</code>
-The ivy dependency file declares only one dependency on apache commons-lang library which by default is a public dependency (see <a href="../../doc/ivyfile.html">ivy file definition</a>).
+The ivy dependency file declares only one dependency on apache commons-lang library which by default is a public dependency (see <a href="../ivyfile.html">ivy file definition</a>).
<h2>the project : depending</h2>
The project depending is very simple too. It declares only one dependency on the latest version of the standalone project and it contains only one class depending.Main which make 2 things:
<ul>
@@ -101,7 +101,7 @@
This tag only load some properties for the ivy process in the same manner as ant will do it.
<h2>the <b>settings</b> tag</h2>
This tag is in charge to initialize some parameters for ivy process. The directory that ivy will use to cache (to store) artifacts found will be in a sub directory called ivy-cache of the directory containing the ivysettings.xml file itself.
-The second parameter, tells ivy to use a resolver called "libraries" as its default resolver. As a recall, a resolver is in charge to resolve an artifact from some information like: the organisation that provides the artifact, the name of the library and the version of the library. More information can be found in the <a href="../../doc/configuration.html">settings documentation</a>.
+The second parameter, tells ivy to use a resolver called "libraries" as its default resolver. As a recall, a resolver is in charge to resolve an artifact from some information like: the organisation that provides the artifact, the name of the library and the version of the library. More information can be found in the <a href="../configuration.html">settings documentation</a>.
<h2>the <b>resolvers</b> tag</h2>
This tag defines the resolvers to use. Here we have two resolvers defined: "projects" and "libraries".
The filesystem resolver called "projects" is able to resolve the internal dependencies wanted.
Modified: incubator/ivy/core/trunk/doc/tutorial/start.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/tutorial/start.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/tutorial/start.html (original)
+++ incubator/ivy/core/trunk/doc/tutorial/start.html Thu Jul 5 07:12:52 2007
@@ -27,7 +27,7 @@
<textarea id="xooki-source">
In this example, we will see one of the easiest way to use ivy. No settings or other complicated files to write, only the list of libraries the project will use.
-If you have already followed the go-ivy tutorial on the <a href="../../doc/tutorial.html">tutorials home page</a>, this tutorial will be already familiar. It is actually pretty much the same, except that it requires ivy to be installed in your ant lib, and the java source and the ivy dependencies are available in separate files. For the java source, it's definitely recommended to put it in a separate file. For ivy dependencies, it depends on your usage and is discussed on the <a href="../../doc/bestpractices.html">best practices page</a>.
+If you have already followed the go-ivy tutorial on the <a href="../tutorial.html">tutorials home page</a>, this tutorial will be already familiar. It is actually pretty much the same, except that it requires ivy to be installed in your ant lib, and the java source and the ivy dependencies are available in separate files. For the java source, it's definitely recommended to put it in a separate file. For ivy dependencies, it depends on your usage and is discussed on the <a href="../bestpractices.html">best practices page</a>.
But enough introduction material, let's go with this simple tutorial!
Modified: incubator/ivy/core/trunk/doc/use/artifactreport.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/artifactreport.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/artifactreport.html (original)
+++ incubator/ivy/core/trunk/doc/use/artifactreport.html Thu Jul 5 07:12:52 2007
@@ -26,15 +26,15 @@
<body>
<textarea id="xooki-source">
<span class="since">since 1.4</span>
-The artifactreport task generates an xml report of all artifacts dependencies resolved by the last <a href="../../doc/use/resolve.html">resolve</a> task call during the same build.
+The artifactreport task generates an xml report of all artifacts dependencies resolved by the last <a href="../use/resolve.html">resolve</a> task call during the same build.
<span class="since">since 2.0</span> This is a [[ant:postresolvetask post resolve task]], with all the behaviour and attributes common to all post resolve tasks.
-This report is different from the standard <a href="../../doc/use/report.html">report</a> which reports all modules and artifacts, whle this report is much simpler and focuses only on artifacts, and gives more information on artifacts, such as the original location and the retrieve location.
+This report is different from the standard <a href="../use/report.html">report</a> which reports all modules and artifacts, whle this report is much simpler and focuses only on artifacts, and gives more information on artifacts, such as the original location and the retrieve location.
It is thus easy to use to generate things like a classpath file for an IDE.
-See this <a href="../../doc/articles/ease-multi-module.html">article by Johan Stuyts</a> (who contributed this task) to see how he uses this task.
+See this <a href="../articles/ease-multi-module.html">article by Johan Stuyts</a> (who contributed this task) to see how he uses this task.
Here is an example of generate file:
<code type="xml">
Modified: incubator/ivy/core/trunk/doc/use/cachefileset.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/cachefileset.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/cachefileset.html (original)
+++ incubator/ivy/core/trunk/doc/use/cachefileset.html Thu Jul 5 07:12:52 2007
@@ -26,7 +26,7 @@
<body>
<textarea id="xooki-source">
Constructs an ant fileset consisting of artifacts in ivy cache for a configuration (<span class="since">since 1.2</span>).<br/><br/>
-This is a <a href="../../doc/use/postresolvetask.html">post resolve task</a>, with all the behaviour and attributes common to all post resolve tasks. Note that this task
+This is a <a href="../use/postresolvetask.html">post resolve task</a>, with all the behaviour and attributes common to all post resolve tasks. Note that this task
does not rely on retrieve, because built fileset is made of artifacts direcly in ivy cache.<br/><br/>
Please prefer the use of retrieve + standard ant path creation, which make your build
more independent from ivy (once artifacts are properly retrieved, ivy is not required any more).<br/><br/>
Modified: incubator/ivy/core/trunk/doc/use/configure.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/configure.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/configure.html (original)
+++ incubator/ivy/core/trunk/doc/use/configure.html Thu Jul 5 07:12:52 2007
@@ -28,7 +28,7 @@
<span class="since">(since 2.0)</span> the configure task is deprecated. Use the <a href="settings.html">setting</a> declaration<br/>
The configure task is used to configure ivy with an xml settings file.<br/><br/>
-See <a href="../../doc/configuration.html">settings</a> for details about the settings file itself.<br/><br/>
+See <a href="../configuration.html">settings</a> for details about the settings file itself.<br/><br/>
<i>Note for developers:<br/>
After the call to this task, a reference to the configured ivy instance used by all subsequent ant tasks is put in the ant project, under the id "ivy.instance".</i>
Modified: incubator/ivy/core/trunk/doc/use/findrevision.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/findrevision.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/findrevision.html (original)
+++ incubator/ivy/core/trunk/doc/use/findrevision.html Thu Jul 5 07:12:52 2007
@@ -28,7 +28,7 @@
<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.
+A version constraint is what is used when declaring a <a href="../ivyfile/dependency.html">dependency</a> on a module.
If the module is not found the property is not set.
<h1>Attributes</h1>
Modified: incubator/ivy/core/trunk/doc/use/info.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/info.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/info.html (original)
+++ incubator/ivy/core/trunk/doc/use/info.html Thu Jul 5 07:12:52 2007
@@ -30,11 +30,11 @@
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>
+<tr><td>ivy.organisation</td><td>The organisation of the module, as found in the <a href="../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="../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="../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="../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="../ivyfile/configurations.html">configurations</a> section</td></tr>
</table>
<h1>Attributes</h1>
Modified: incubator/ivy/core/trunk/doc/use/install.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/install.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/install.html (original)
+++ incubator/ivy/core/trunk/doc/use/install.html Thu Jul 5 07:12:52 2007
@@ -31,7 +31,7 @@
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>
+For more details about this task and its usage see the <a href="../tutorial/build-repository.html">build repository tutorial</a>
<table class="ant">
<thead>
Modified: incubator/ivy/core/trunk/doc/use/listmodules.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/listmodules.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/listmodules.html (original)
+++ incubator/ivy/core/trunk/doc/use/listmodules.html Thu Jul 5 07:12:52 2007
@@ -30,7 +30,7 @@
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>.
+To know if a module matches the criteria ivy will use the configured <a href="../concept#matcher.html">pattern matcher</a>.
<h1>Attributes</h1>
<table class="ant">
Modified: incubator/ivy/core/trunk/doc/use/publish.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/publish.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/publish.html (original)
+++ incubator/ivy/core/trunk/doc/use/publish.html Thu Jul 5 07:12:52 2007
@@ -29,7 +29,7 @@
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.
+The repository is given through the name of a resolver declared in current ivy configuration. See <a href="../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>
Modified: incubator/ivy/core/trunk/doc/use/report.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/report.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/report.html (original)
+++ incubator/ivy/core/trunk/doc/use/report.html Thu Jul 5 07:12:52 2007
@@ -32,7 +32,7 @@
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>.
+Then following a few <a href="../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.
Modified: incubator/ivy/core/trunk/doc/use/repreport.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/repreport.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/repreport.html (original)
+++ incubator/ivy/core/trunk/doc/use/repreport.html Thu Jul 5 07:12:52 2007
@@ -31,7 +31,7 @@
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.
+Usually the most useful report is a graph, you can generate either a graphml file that you can then easily <a href="../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>
Modified: incubator/ivy/core/trunk/doc/use/resolve.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/resolve.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/resolve.html (original)
+++ incubator/ivy/core/trunk/doc/use/resolve.html Thu Jul 5 07:12:52 2007
@@ -25,7 +25,7 @@
</head>
<body>
<textarea id="xooki-source">
-The resolve task actually resolve dependencies described in an <a href="../../doc/ivyfile.html">ivy file</a>, and put the resolved dependencies in the ivy cache.
+The resolve task actually resolve dependencies described in an <a href="../ivyfile.html">ivy file</a>, and put the resolved dependencies in the ivy cache.
If configure has not been called before resolve is called, a default configuration will be used (equivalent to call configure with no attributes).
After the call to this task, four properties are set in ant:
Modified: incubator/ivy/core/trunk/doc/use/settings.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/settings.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/settings.html (original)
+++ incubator/ivy/core/trunk/doc/use/settings.html Thu Jul 5 07:12:52 2007
@@ -28,7 +28,7 @@
The settings declaration is used to configure ivy with an xml settings file.<br/><br/>
-See <a href="../../doc/doc/configuration.html">Settings Files</a> for details about the settings file itself.<br/><br/>
+See <a href="../doc/configuration.html">Settings Files</a> for details about the settings file itself.<br/><br/>
Multiple settings can be defined in a build script. Every task can reference his own settings.<br/><br/>
Modified: incubator/ivy/core/trunk/doc/use/var.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/use/var.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/use/var.html (original)
+++ incubator/ivy/core/trunk/doc/use/var.html Thu Jul 5 07:12:52 2007
@@ -30,7 +30,7 @@
Contrary to ant properties, ivy variables are mutable. But a problem with this is that you do not control when
variables are substituted, and usually it is done as soon as possible. So changing the value of a variable will
have no effect if it has already been substituted. Consequently, <b>using this task is NOT recommended</b>.
-See <a href="../../doc/reference.html">reference</a> page for details about ivy variables.
+See <a href="../reference.html">reference</a> page for details about ivy variables.
<br/><br/>
<table class="ant">
Modified: incubator/ivy/core/trunk/doc/yed.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/yed.html?view=diff&rev=553512&r1=553511&r2=553512
==============================================================================
--- incubator/ivy/core/trunk/doc/yed.html (original)
+++ incubator/ivy/core/trunk/doc/yed.html Thu Jul 5 07:12:52 2007
@@ -31,7 +31,7 @@
The graphs generated by ivy are not layed out (in fact it's why we use yEd), so you have to follow a simple sequence of steps to layout the generated graphs.
<h2>Preparation</h2>
-First you have to generate a graphml file. Simply call the report task (see <a href="../doc/use.html">ivy use documentation</a>) for that.
+First you have to generate a graphml file. Simply call the report task (see <a href="use.html">ivy use documentation</a>) for that.
<h2>Step 1: open the graphml file</h2>
Launch yEd editor, and open the graphml file generated by the report task. You should obtain something like this: