Author: xavier
Date: Wed Jun 25 02:55:28 2008
New Revision: 671490
URL: http://svn.apache.org/viewvc?rev=671490&view=rev
Log:
document m2compatible listing limitation (related to IVY-503)
Modified:
ant/ivy/core/trunk/doc/resolver/filesystem.html
ant/ivy/core/trunk/doc/resolver/ibiblio.html
ant/ivy/core/trunk/doc/resolver/url.html
ant/ivy/core/trunk/doc/use/repreport.html
Modified: ant/ivy/core/trunk/doc/resolver/filesystem.html
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/resolver/filesystem.html?rev=671490&r1=671489&r2=671490&view=diff
==============================================================================
--- ant/ivy/core/trunk/doc/resolver/filesystem.html (original)
+++ ant/ivy/core/trunk/doc/resolver/filesystem.html Wed Jun 25 02:55:28 2008
@@ -36,6 +36,7 @@
The configuration of such a resolver is mainly done through ivy and artifact
patterns, indicating where ivy files and artifacts can be found in the file
system. You can indicate a list of pattern which will be checked one after the
other.
<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.
+<strong>Limitation</strong>: in m2compatible mode, this resolver is not able
list available organizations. It means some features like [[ant:repreport]] are
not available.
<h2>Atomic publish support</h2>
<span class="since">since 2.0</span> This resolver supports atomic publish,
which is very suitable for environments with a lot of concurrent publish and
resolve. The atomic publish relies on the atomicity of the rename operation in
the underlying filesystem (which includes NTFS and POSIX based filesystems).
Modified: ant/ivy/core/trunk/doc/resolver/ibiblio.html
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/resolver/ibiblio.html?rev=671490&r1=671489&r2=671490&view=diff
==============================================================================
--- ant/ivy/core/trunk/doc/resolver/ibiblio.html (original)
+++ ant/ivy/core/trunk/doc/resolver/ibiblio.html Wed Jun 25 02:55:28 2008
@@ -44,6 +44,8 @@
<span class="since">since 2.0</span> When used in m2compatible mode with the
default pattern, this resolver uses maven-metadata.xml files if present to list
the revisions available on the repository. This is especially useful when using
a maven specific proxy, which does not serve directory listing. This can be
disable by using the useMavenMetadata flag.
+<strong>Limitation</strong>: in m2compatible mode, this resolver is not able
list available organizations. It means some features like [[ant:repreport]] are
not available.
+
<h1>Attributes</h1>
This resolver shares the <a
href="../configuration/resolvers.html#common">common attributes</a> of standard
resolvers.
<table class="ivy-attributes">
Modified: ant/ivy/core/trunk/doc/resolver/url.html
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/resolver/url.html?rev=671490&r1=671489&r2=671490&view=diff
==============================================================================
--- ant/ivy/core/trunk/doc/resolver/url.html (original)
+++ ant/ivy/core/trunk/doc/resolver/url.html Wed Jun 25 02:55:28 2008
@@ -34,6 +34,8 @@
<br/>
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.
+<strong>Limitation</strong>: in m2compatible mode, this resolver is not able
list available organizations. It means some features like [[ant:repreport]] are
not available.
+
<h1>Attributes</h1>
This resolver shares the <a
href="../configuration/resolvers.html#common">common attributes</a> of standard
resolvers.
<table class="ivy-attributes">
Modified: ant/ivy/core/trunk/doc/use/repreport.html
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/doc/use/repreport.html?rev=671490&r1=671489&r2=671490&view=diff
==============================================================================
--- ant/ivy/core/trunk/doc/use/repreport.html (original)
+++ ant/ivy/core/trunk/doc/use/repreport.html Wed Jun 25 02:55:28 2008
@@ -33,6 +33,8 @@
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.
+<strong>Limitation</strong>: this task requires to be able to browse the
repository, and is thus limited to resolvers supporting repository listing. In
particular, it means it doesn't work to report all organizations in a
repository using m2compatible mode.
+
<table class="ant">
<thead>
<tr><th class="ant-att">Attribute</th><th
class="ant-desc">Description</th><th class="ant-req">Required</th></tr>
