incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xav...@apache.org
Subject svn commit: r536488 [10/19] - in /incubator/ivy/core/trunk: ./ doc/ doc/doc/ doc/doc/configuration/ doc/doc/configuration/macrodef/ doc/doc/configuration/namespace/ doc/doc/ivyfile/ doc/doc/releasenotes/ doc/doc/resolver/ doc/doc/tutorial/ doc/doc/tuto...
Date Wed, 09 May 2007 10:58:16 GMT
Modified: incubator/ivy/core/trunk/doc/doc/releasenotes/1.4-RC2.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/releasenotes/1.4-RC2.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/releasenotes/1.4-RC2.html (original)
+++ incubator/ivy/core/trunk/doc/doc/releasenotes/1.4-RC2.html Wed May  9 03:58:10 2007
@@ -1,50 +1,50 @@
-<!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">
-Here are the release notes of version 1.4-RC2.
-A new and noteworthy section is available on <a href="../../doc/releasenotes/1.4.html">version 1.4 page</a>.
-
-You can download it here:
-<ul><li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-bin.zip">binaries</a></li>
-<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-src.zip">sources</a></li>
-<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-doc.zip">documentation</a></li>
-</ul>
-
-It includes only bug fixes since 1.4-RC1.
-<code>
-   version 1.4-RC2 - 2006-09-27
-=====================================
-- FIX: m2compatible flag is ignored for display of failed artifact searches (IVY-303)
-- FIX: AntCallTriggerTest and AntBuildTriggerTest fail when run from ivy build.xml (IVY-310)
-- FIX: Classloader problem with ant (IVY-311)
-- FIX: Make resolve overview more compact (IVY-299)
-- FIX: Could not write to "tmp:///webdav_tmp.c1" because it is read-only (IVY-312)
-</code>
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Here are the release notes of version 1.4-RC2.
+A new and noteworthy section is available on <a href="../../doc/releasenotes/1.4.html">version 1.4 page</a>.
+
+You can download it here:
+<ul><li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-bin.zip">binaries</a></li>
+<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-src.zip">sources</a></li>
+<li><a href="http://www.jayasoft.org/downloads/ivy/1.4-RC2/ivy-1.4-RC2-doc.zip">documentation</a></li>
+</ul>
+
+It includes only bug fixes since 1.4-RC1.
+<code>
+   version 1.4-RC2 - 2006-09-27
+=====================================
+- FIX: m2compatible flag is ignored for display of failed artifact searches (IVY-303)
+- FIX: AntCallTriggerTest and AntBuildTriggerTest fail when run from ivy build.xml (IVY-310)
+- FIX: Classloader problem with ant (IVY-311)
+- FIX: Make resolve overview more compact (IVY-299)
+- FIX: Could not write to "tmp:///webdav_tmp.c1" because it is read-only (IVY-312)
+</code>
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/releasenotes/1.4-RC2.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.1.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.1.html (original)
+++ incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.1.html Wed May  9 03:58:10 2007
@@ -1,57 +1,57 @@
-<!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">
-Ivy 1.4.1 is mainly a bug fix version, upgrade from 1.4 is strongly recommended.
-
-It has been released on 2006-11-09.
-
-<h1>Downloads</h1>
-<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-bin.zip">ivy-1.4.1-bin.zip</a>
-<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-src.zip">ivy-1.4.1-src.zip</a>
-<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-doc.zip">ivy-1.4.1-doc.zip</a>
-
-<h1>Changes log</h1>
-<pre>
-- IMPROVE: ability to rebuild all dependent projects from a leaf (IVY-101)
-- IMPROVE: Artifact pattern list attribute for the ivy:publish (IVY-113)
-- IMPROVE: Measure code coverage (IVY-323)
-- IMPROVE: add release target to build file (IVY-339)
-- IMPROVE: Add a 'conf' parameter to the ivy 'publish' ant task (IVY-322) (thanks to Emmanuel Pellereau)
-
-- FIX: retrieve fails when resolve is done with useOrigin set to true (IVY-304)
-- FIX: IVY complains about non-existent reports in the cache directory (IVY-315)
-- FIX: Typo in failureproperty attribute of Ant resolve task (IVY-327) (thanks to Jean-Baptiste Quenot)
-- FIX: ivy:resolve useOrigin fails to behave correctly (IVY-332)
-- FIX: ChainVersionMatcher doesn't handle IvyAware children version matchers (IVY-331)
-- FIX: latest.&lt;status> does not work properly when no matching revision exist (IVY-318)
-- FIX: attribute name in macrodef is not handled as expected (IVY-319)
-- FIX: confmappingoverride doesn't work for configurations extending from "*(public)" (IVY-326)
-</pre>
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Ivy 1.4.1 is mainly a bug fix version, upgrade from 1.4 is strongly recommended.
+
+It has been released on 2006-11-09.
+
+<h1>Downloads</h1>
+<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-bin.zip">ivy-1.4.1-bin.zip</a>
+<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-src.zip">ivy-1.4.1-src.zip</a>
+<a href="http://www.jayasoft.org/downloads/ivy/1.4.1/ivy-1.4.1-doc.zip">ivy-1.4.1-doc.zip</a>
+
+<h1>Changes log</h1>
+<pre>
+- IMPROVE: ability to rebuild all dependent projects from a leaf (IVY-101)
+- IMPROVE: Artifact pattern list attribute for the ivy:publish (IVY-113)
+- IMPROVE: Measure code coverage (IVY-323)
+- IMPROVE: add release target to build file (IVY-339)
+- IMPROVE: Add a 'conf' parameter to the ivy 'publish' ant task (IVY-322) (thanks to Emmanuel Pellereau)
+
+- FIX: retrieve fails when resolve is done with useOrigin set to true (IVY-304)
+- FIX: IVY complains about non-existent reports in the cache directory (IVY-315)
+- FIX: Typo in failureproperty attribute of Ant resolve task (IVY-327) (thanks to Jean-Baptiste Quenot)
+- FIX: ivy:resolve useOrigin fails to behave correctly (IVY-332)
+- FIX: ChainVersionMatcher doesn't handle IvyAware children version matchers (IVY-331)
+- FIX: latest.&lt;status> does not work properly when no matching revision exist (IVY-318)
+- FIX: attribute name in macrodef is not handled as expected (IVY-319)
+- FIX: confmappingoverride doesn't work for configurations extending from "*(public)" (IVY-326)
+</pre>
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

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

Modified: incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.html (original)
+++ incubator/ivy/core/trunk/doc/doc/releasenotes/1.4.html Wed May  9 03:58:10 2007
@@ -1,339 +1,339 @@
-<!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">
-<h1>Changes log</h1>
-Ivy 1.4-RC2 has been promoted to 1.4 on 2006-10-09
-
-Known bugs and limitations:
-- references in resolvers are not resolved 'in-time' with macrodef (IVY-319)
-- latest.<status> does not work properly when no matching revision exist (IVY-318)
-- IVY complains about non-existent reports in the cache directory (IVY-315)
-- retrieve fails when resolve is done with useOrigin set to true (IVY-304)
-
-For detailed list of changes since 1.3.1, please see changes of the two release candidates detailed in child pages.
-For an overview of what's new and noteworthy in this release since 1.3 see the new and noteworthy section below.
-
-<h1>Downloads</h1>
-<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-bin.zip">ivy-1.4-bin.zip</a>
-<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-src.zip">ivy-1.4-src.zip</a>
-<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-doc.zip">ivy-1.4-doc.zip</a>
-
-<div class="newandnoteworthy">
-<h1><center><big>New and noteworthy</big></center></h1>
-<h1>Documentation</h1>
-<h2>A new introduction tutorial as simple as 1-2-3</h2>
-It has never been so easy to try Ivy! You don't even need to install it yourself! Follow this simple steps and you're done:
-<ol>
-<li>make sure you have <a href="http://ant.apache.org/">ant</a> 1.6.2 or greater and a <a href="http://java.sun.com">jdk</a> properly installed</li>
-<li>copy [[svn:src/example/go-ivy/build.xml this build file]] in an empty directory on your local filesystem (and make sure you name it build.xml)</li>
-<li>open a console in this directory and run "ant". That's it!</li>
-</ol>
-If you have any trouble, check the <a href="../../faq.html">FAQ</a>, it may be related to your internet connection (proxy anyone?).
-Want to try more tutorials? Check the <a href="../../doc/tutorial.html">tutorials</a> page in the documentation.
-<h2>Offline documentation greatly improved</h2>
-The offline documentation has been greatly improved, and is now a real copy of the online documentation, with all the navigation between pages as on the online version. Continue to use the online version when you can to have the latest updated version with user comments.
-<h2>Documentation update</h2>
-As usual, the documentation has been extensively updated with to reflect the new features. Some are still missing, but we will finish the update before the 1.4 release.
-
-Moreover, more examples have been added, more links between the pages, and some very useful pages have been added like the <a href="../../doc/bestpractices.html">best practices</a> one.
-<h1>Core features</h1>
-<h2><a href="../../doc/concept.html#extra">Extra attributes</a></h2>
-Several tags in ivy xml files are now extensible with extra attributes. 
-
-The idea is very simple: if you need some more information to define your modules, you can add the attribute you want and you will then be able to access it as any other attribute in your patterns for example.
-
-Example:
-Here is an ivy file with the attribute 'color' set to blue:
-<code type="xml">
-<ivy-module version="1.4">
-	<info organisation="jayasoft"
-	       module="foo"
-	       color="blue"
-	       status="integration"
-	       revision="1.59"
-	/>
-</ivy-module>
-</code>
-Then you can use the extra attribute when you declare a dependency on foo:
-<code>
-<dependency org="jayasoft" name="foo" color="blue" rev="1.5+" />
-</code>
-And you can define your repository pattern as:
-<code>
-${repository.dir}/[organisation]/[module]/[color]/[revision]/[artifact].[ext]
-</code>
-
-Note that in order to use extra attributes, you will need to disable ivy file validation, since your files won't fulffill anymore the official ivy xsd. See the <a href="../../doc/configuration/conf.html">configuration doc page</a> to see how to disable validation.
-
-<h2><a href="../../doc/ivyfile/dependency.html">Version matchers</a></h2>
-Ivy now rely on a new concept to specify which version of a dependency should be used: pluggable version matchers.
-This means that you can define your own way to match a dependency version.
-
-Both latest.integration and latest sub version (1.3+ for instance) have been ported to this mechanism.
-
-With this new feature Ivy also comes with two new built-in version matchers:
-<ul>
-<li>latest.[any status]</li>selects the latest revision of the dependency module with at least the specified status.
-<li>version ranges</li>You can now express your version contraint as a mathematical range.
-</ul>
-
-Examples:
-<code type="xml">
-<dependency org="foo" name="bar" rev="latest.milestone" />
-</code>
-Will find the latest version of bar which is in milestone or release status.
-<code type="xml">
-<dependency org="foo" name="bar" rev="[1.0,2.0]" />
-</code>
-Matches any revision greater than 1.0 and lower than 2.0, inclusive.
-
-<h2><a href="../../doc/ivyfile/dependency-artifact.html">URL attribute on artifact to improve ease of use</a></h2>
-The artifact tag used when declaring a dependency now supports an url attribute. Even if this should be used only in very special cases (because it derrogates to the standard repository management), it can be useful, well, in very special cases :-)
-
-Example:
-<code type="xml">
-<dependency org="foo" name="bar" rev="1.0">
-  <artifact name="baz" type="jar" url="http://www.acme.com/repository/bar/baz-1.0-acme.jar"/>
-</dependency>
-</code>
-
-<h2><a href="../../doc/ivyfile/conf.html">Module configurations enhancements</a></h2>
-Several improvements have been made on the module configurations:
-<ul><li>It is now possible to disable transitivity for a whole configuration.
-
-Example:
-<code type="xml">
-<conf name="compile" extends="core" transitive="false" visibility="private" />
-</code></li>
-<li>You can use <code>*</code>, <code>*(public)</code> or <code>*(private)</code> as wildcards to extend a set of configurations.
-
-Example:
-<code type="xml">
-<conf name="all" extends="*" />
-</code></li>
-<li>You can use <code>*, !A, !B</code> in configurations mapping to mean all configurations but A and B.
-
-Example:
-<code type="xml">
-<dependency name="commons-lang" rev="1.0" conf="*, !deploy->default" />
-</code></li>
-</ul>
-
-<h2><a href="../../doc/concept.html#event">Events and triggers</a></h2>
-Ivy now fires events all along the dependency resolution process, which can be listened and which can trigger events.
-
-Example:
-<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 just before resolving a dependency with a latest.integration revision.
-
-<h1>New Resolvers</h1>
-<h2><a href="../../doc/resolver/vfs.html">vfs</a></h2>
-The new vfs resolver leverages the work from <a href="http://jakarta.apache.org/commons/vfs/">apache commons vfs</a> to give a uniform access to a set of different file systems including ftp, sftp, webdav, zip, ...
-
-Example:
-<code type="xml">
-<vfs name="remote">
-  <ivy pattern="webdav://username:password@host:8080/[organisation]/[module]/[revision]/ivy.xml" />
-  <artifact pattern="webdav://username:password@host:8080/[organisation]/[module]/[revision]/[artifact].[ext]" />
-</vfs>
-</code>
-
-<h2><a href="../../doc/resolver/ssh.html">ssh</a> and <a href="../../doc/resolver/sftp.html">sftp</a></h2>
-The new ssh and sftp resolvers allow, as their name suggest, to access a repository using ssh or sftp. The secured nature of ssh and its wide spread implementation on most *nix servers makes these resolvers very good candidate in an enterprise environment.
-
-Example:
-<code type="xml">
-<sftp name="secured" keyFile="path/to/key/file" keyFilePassword="${password}">
-  <ivy pattern="sftp://user:xavier@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
-  <artifact pattern="sftp://user:xavier@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
-</sftp>
-</code>
-
-<h1>Configuration files</h1>
-<h2><a href="../../doc/configuration/statuses.html">Configurable statuses</a></h2>
-The list of statuses available in module files is now configurable.
-
-Example:
-<code type="xml">
-<statuses default="bronze">
-  <status name="gold" integration="false"/>
-  <status name="silver" integration="false"/>
-  <status name="bronze" integration="true"/>
-</statuses>
-</code>
-<h2><a href="../../doc/configuration/module.html">Per module settings</a></h2>
-It is now possible possible to configure conflict-manager per module set.
-
-Example:
-<code type="xml">
-<modules>
-  <module organisation="jayasoft" name="ivy*" matcher="glob" conflict-manager="latest-time"/>
-</modules>
-</code>
-<h2><a href="../../doc/concept#checksum.html">Checksums</a></h2>
-Ivy now allow to use checksums to verify the correctness of a downloaded file.
-
-For the moment Ivy supports md5 and sha1 algorithm.
-
-The configuration of using md5 and/or sha1 can be done globally or by dependency resolver.
-Globally, use the ivy.checksums variable to list the check to be done (only md5 and sha1 are supported).
-On each resolver you can use the checksums attribute to override the global setting.
-
-The setting is a comma separated list of checksum algorithm to use.
-During checking (at download time), the first checksum found is checked, and that's all. This means that if you have a "sha1, md5" setting, then if ivy finds a sha1 file, it will compare the downloaded file sha1 against this sha1, and if the comparison is ok, it will assume the file is ok. If no sha1 file is found, it will look for a md5 file. If none is found no checking is done.
-During publish, all listed checksum algorithms are computed and uploaded.
-
-By default checksum algorithms are "sha1, md5".
-<h2><a href="../../doc/configuration/resolvers#common.html">Fail when no module descriptor is found</a></h2>
-By default when ivy doesn't find a module descriptor for a module, it lloks for an artifact, and if it finds one it assumes a default module descriptor. 
-It is now possible to configure this behaviour per resolver, by setting the allownomd attribute to false you can force the use of a module descriptor, and fail if none is found. This is also useful to improve performances on a resolver for which you know you will always have module descriptors.
-<h2>System properties</h2>
-All java system properties are now available as ivy variables in your configuration files.
-Thus you can now easily define the default cache relative to user home (using ${user.home}), or access any specific property set via the standard java system property mechanism.
-
-<h2><a href="../../doc/configuration/resolvers#common.html">Changing pattern</a></h2>
-You can now define a changingPattern and a changingMatcher to configure a set of revisions which should always be considered as changing one (artifacts are checked to see if they are up to date).
-
-The pattern and the matcher name are attributes available on all built-in resolvers.
-
-Example:
-<code type="xml">
-<filesystem name="local" changingPattern="*-SNAPSHOT" changingMatcher="glob">
-</code>
-will consider all modules with a revision ending by SNAPSHOT to be changing revisions.
-
-<h2><a href="../../doc/configuration/classpath.html">Customisable classpath</a></h2>
-You can now add jars to use to load plugins directly in ivy configuration, so that you can easily use your plugins in several execution environment (ant, standalone, IDE plugin, ...).
-
-Example:
-<code type="xml">
-<ivyconf>
-  <classpath file="${ivy.settings.dir}/custom-resolver.jar"/>
-  <typedef name="custom" classname="fr.jayasoft.ivy.resolver.CustomResolver"/>
-  <resolvers>
-    <custom name="custom"/>
-  </resolvers>
-</ivyconf>
-</code>
-
-<h1>Ant tasks</h1>
-<h2><a href="../../doc/use/repreport.html">repreport</a></h2>
-A new repreport task allows to generate reports directly from your repository. The graph generation is the most interesting one, it can gives you a good overview of the dependencies between of all your modules available in your repository, or restrict this graph to just the modules from this organisation, and so on.
-
-Example:
-<code type="xml">
-<ivy:repreport organisation="myorg" xml="false" graph="true" />
-will generate a graphml of dependencies with all modules in the organisation "myorg"
-</code>
-
-<h2><a href="../../doc/use/artifactreport.html">artifactreport</a></h2>
-A new artifactreport task has been introduced to easily generate an xml report with artifacts resolved, with useful information such as their original location. This report is particularly well suited for generating IDE classpaths (see also the <a href="../../links.html">links</a> page for higher IDE integration via plugins).
-
-The generated report looks like this:
-<code type="xml">
-<?xml version="1.0" encoding="UTF-8"?>
-<modules>
-  <module organisation="hippo" name="sant-classes" rev="1.01.00b04-dev" status="integration">
-    <artifact name="sant-classes-src" ext="zip" type="zip">
-      <origin-location is-local="true">
-        C:/home/jstuyts/data/ivy/local/hippo/sant-classes/1.01.00b04-dev/sant-classes-src-1.01.00b04-dev.zip</origin-location>
-      <cache-location>
-        C:/home/jstuyts/data/ivy/cache/hippo/sant-classes/zips/sant-classes-src-1.01.00b04-dev.zip</cache-location>
-      <retrieve-location>lib/test/sant-classes-src-1.01.00b04-dev.zip</retrieve-location>
-    </artifact>
-  </module>
-  <module organisation="testng" name="testng" rev="4.6.1-jdk15" status="release">
-    <artifact name="testng" ext="jar" type="jar">
-      <origin-location is-local="false">
-        http://repository.hippocms.org/maven/testng/jars/testng-4.6.1-jdk15.jar</origin-location>
-      <cache-location>C:/home/jstuyts/data/ivy/cache/testng/testng/jars/testng-4.6.1-jdk15.jar</cache-location>
-      <retrieve-location>lib/test/testng-4.6.1-jdk15.jar</retrieve-location>
-    </artifact>
-  </module>
-</code>
-
-<h2><a href="../../doc/use/info.html">info</a></h2>
-The new info task eases the access to some essential data contained in an ivy file without performing a dependency resolution.
-
-Example:
-<code type="xml">
-<ivy:info file="${basedir}/path/to/ivy.xml" />
-</code>
-
-<h2><a href="../../doc/use/listmodules.html">listmodules</a></h2>
-The new listmodules task let you list modules available in the repository and set ant properties accordingly.
-
-Example:
-<code type="xml">
-<ivy:listmodules organisation="jayasoft" module="ivy" revision="*" property="ivy.[revision]" value=="found"/>
-</code>
-
-<h2><a href="../../doc/use/findrevision.html">findrevision</a></h2>
-This new task sets an ant property with the latest revision found for a given module matching a given revision constraint.
-
-<code type="xml">
-<ivy:findrevision organisation="jayasoft" module="ivy" revision="1.0+"/>
-</code>
-
-<h2><a href="../../doc/use/resolve.html">useOrigin</a></h2>
-The resolve, cachepath, and retrieve tasks now supports a new useOrigin attribute, which allow to use the original location of local artifacts instead of their location in ivy cache. Used directly on a resolve or when no resolve has been done, it will avoid the copy of the artifact to the cache, and use directly the artifact from its original location.
-
-<code type="xml">
-<cachepath pathid="default.classpath" conf="default" useOrigin="true" />
-</code>
-<h2><a href="../../doc/use/resolve.html">Disable transitive dependencies on resolve</a></h2>
-You can now disable transitive dependencies on resolve.
-
-Example:
-<code type="xml">
-<ivy:resolve file="path/to/ivy.xml" transitive="false" />
-</code>
-<h2><a href="../../doc/use/retrieve.html">Synchronization feature in retrieve</a></h2>
-The retrieve task can now performs a real synchronization of the destination directory, instead of a simple copy.
-
-Example:
-<code type="xml">
-<ivy:retrieve pattern="${lib.dir}/[conf]/[artifact].[ext]" sync="true" />
-</code>
-
-<h1>Standalone mode</h1>
-<h2>Application launcher</h2>
-Ivy can now be used as an application launcher:
-<code>
-java fr.jayasoft.ivy.Main -conf path/to/myivyconf.xml -dependency bar foo 2.0 -main org.bar.foo.FooMain
-</code>
-calls ivy with given ivyconf file and resolve bar foo 2.0, and then run org.foo.FooMain class with the resolved artifacts (foo 2.0 and its dependencies) as classpath
-</div>
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<h1>Changes log</h1>
+Ivy 1.4-RC2 has been promoted to 1.4 on 2006-10-09
+
+Known bugs and limitations:
+- references in resolvers are not resolved 'in-time' with macrodef (IVY-319)
+- latest.<status> does not work properly when no matching revision exist (IVY-318)
+- IVY complains about non-existent reports in the cache directory (IVY-315)
+- retrieve fails when resolve is done with useOrigin set to true (IVY-304)
+
+For detailed list of changes since 1.3.1, please see changes of the two release candidates detailed in child pages.
+For an overview of what's new and noteworthy in this release since 1.3 see the new and noteworthy section below.
+
+<h1>Downloads</h1>
+<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-bin.zip">ivy-1.4-bin.zip</a>
+<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-src.zip">ivy-1.4-src.zip</a>
+<a href="http://www.jayasoft.org/downloads/ivy/1.4/ivy-1.4-doc.zip">ivy-1.4-doc.zip</a>
+
+<div class="newandnoteworthy">
+<h1><center><big>New and noteworthy</big></center></h1>
+<h1>Documentation</h1>
+<h2>A new introduction tutorial as simple as 1-2-3</h2>
+It has never been so easy to try Ivy! You don't even need to install it yourself! Follow this simple steps and you're done:
+<ol>
+<li>make sure you have <a href="http://ant.apache.org/">ant</a> 1.6.2 or greater and a <a href="http://java.sun.com">jdk</a> properly installed</li>
+<li>copy [[svn:src/example/go-ivy/build.xml this build file]] in an empty directory on your local filesystem (and make sure you name it build.xml)</li>
+<li>open a console in this directory and run "ant". That's it!</li>
+</ol>
+If you have any trouble, check the <a href="../../faq.html">FAQ</a>, it may be related to your internet connection (proxy anyone?).
+Want to try more tutorials? Check the <a href="../../doc/tutorial.html">tutorials</a> page in the documentation.
+<h2>Offline documentation greatly improved</h2>
+The offline documentation has been greatly improved, and is now a real copy of the online documentation, with all the navigation between pages as on the online version. Continue to use the online version when you can to have the latest updated version with user comments.
+<h2>Documentation update</h2>
+As usual, the documentation has been extensively updated with to reflect the new features. Some are still missing, but we will finish the update before the 1.4 release.
+
+Moreover, more examples have been added, more links between the pages, and some very useful pages have been added like the <a href="../../doc/bestpractices.html">best practices</a> one.
+<h1>Core features</h1>
+<h2><a href="../../doc/concept.html#extra">Extra attributes</a></h2>
+Several tags in ivy xml files are now extensible with extra attributes. 
+
+The idea is very simple: if you need some more information to define your modules, you can add the attribute you want and you will then be able to access it as any other attribute in your patterns for example.
+
+Example:
+Here is an ivy file with the attribute 'color' set to blue:
+<code type="xml">
+<ivy-module version="1.4">
+	<info organisation="jayasoft"
+	       module="foo"
+	       color="blue"
+	       status="integration"
+	       revision="1.59"
+	/>
+</ivy-module>
+</code>
+Then you can use the extra attribute when you declare a dependency on foo:
+<code>
+<dependency org="jayasoft" name="foo" color="blue" rev="1.5+" />
+</code>
+And you can define your repository pattern as:
+<code>
+${repository.dir}/[organisation]/[module]/[color]/[revision]/[artifact].[ext]
+</code>
+
+Note that in order to use extra attributes, you will need to disable ivy file validation, since your files won't fulffill anymore the official ivy xsd. See the <a href="../../doc/configuration/conf.html">configuration doc page</a> to see how to disable validation.
+
+<h2><a href="../../doc/ivyfile/dependency.html">Version matchers</a></h2>
+Ivy now rely on a new concept to specify which version of a dependency should be used: pluggable version matchers.
+This means that you can define your own way to match a dependency version.
+
+Both latest.integration and latest sub version (1.3+ for instance) have been ported to this mechanism.
+
+With this new feature Ivy also comes with two new built-in version matchers:
+<ul>
+<li>latest.[any status]</li>selects the latest revision of the dependency module with at least the specified status.
+<li>version ranges</li>You can now express your version contraint as a mathematical range.
+</ul>
+
+Examples:
+<code type="xml">
+<dependency org="foo" name="bar" rev="latest.milestone" />
+</code>
+Will find the latest version of bar which is in milestone or release status.
+<code type="xml">
+<dependency org="foo" name="bar" rev="[1.0,2.0]" />
+</code>
+Matches any revision greater than 1.0 and lower than 2.0, inclusive.
+
+<h2><a href="../../doc/ivyfile/dependency-artifact.html">URL attribute on artifact to improve ease of use</a></h2>
+The artifact tag used when declaring a dependency now supports an url attribute. Even if this should be used only in very special cases (because it derrogates to the standard repository management), it can be useful, well, in very special cases :-)
+
+Example:
+<code type="xml">
+<dependency org="foo" name="bar" rev="1.0">
+  <artifact name="baz" type="jar" url="http://www.acme.com/repository/bar/baz-1.0-acme.jar"/>
+</dependency>
+</code>
+
+<h2><a href="../../doc/ivyfile/conf.html">Module configurations enhancements</a></h2>
+Several improvements have been made on the module configurations:
+<ul><li>It is now possible to disable transitivity for a whole configuration.
+
+Example:
+<code type="xml">
+<conf name="compile" extends="core" transitive="false" visibility="private" />
+</code></li>
+<li>You can use <code>*</code>, <code>*(public)</code> or <code>*(private)</code> as wildcards to extend a set of configurations.
+
+Example:
+<code type="xml">
+<conf name="all" extends="*" />
+</code></li>
+<li>You can use <code>*, !A, !B</code> in configurations mapping to mean all configurations but A and B.
+
+Example:
+<code type="xml">
+<dependency name="commons-lang" rev="1.0" conf="*, !deploy->default" />
+</code></li>
+</ul>
+
+<h2><a href="../../doc/concept.html#event">Events and triggers</a></h2>
+Ivy now fires events all along the dependency resolution process, which can be listened and which can trigger events.
+
+Example:
+<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 just before resolving a dependency with a latest.integration revision.
+
+<h1>New Resolvers</h1>
+<h2><a href="../../doc/resolver/vfs.html">vfs</a></h2>
+The new vfs resolver leverages the work from <a href="http://jakarta.apache.org/commons/vfs/">apache commons vfs</a> to give a uniform access to a set of different file systems including ftp, sftp, webdav, zip, ...
+
+Example:
+<code type="xml">
+<vfs name="remote">
+  <ivy pattern="webdav://username:password@host:8080/[organisation]/[module]/[revision]/ivy.xml" />
+  <artifact pattern="webdav://username:password@host:8080/[organisation]/[module]/[revision]/[artifact].[ext]" />
+</vfs>
+</code>
+
+<h2><a href="../../doc/resolver/ssh.html">ssh</a> and <a href="../../doc/resolver/sftp.html">sftp</a></h2>
+The new ssh and sftp resolvers allow, as their name suggest, to access a repository using ssh or sftp. The secured nature of ssh and its wide spread implementation on most *nix servers makes these resolvers very good candidate in an enterprise environment.
+
+Example:
+<code type="xml">
+<sftp name="secured" keyFile="path/to/key/file" keyFilePassword="${password}">
+  <ivy pattern="sftp://user:xavier@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
+  <artifact pattern="sftp://user:xavier@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
+</sftp>
+</code>
+
+<h1>Configuration files</h1>
+<h2><a href="../../doc/configuration/statuses.html">Configurable statuses</a></h2>
+The list of statuses available in module files is now configurable.
+
+Example:
+<code type="xml">
+<statuses default="bronze">
+  <status name="gold" integration="false"/>
+  <status name="silver" integration="false"/>
+  <status name="bronze" integration="true"/>
+</statuses>
+</code>
+<h2><a href="../../doc/configuration/module.html">Per module settings</a></h2>
+It is now possible possible to configure conflict-manager per module set.
+
+Example:
+<code type="xml">
+<modules>
+  <module organisation="jayasoft" name="ivy*" matcher="glob" conflict-manager="latest-time"/>
+</modules>
+</code>
+<h2><a href="../../doc/concept#checksum.html">Checksums</a></h2>
+Ivy now allow to use checksums to verify the correctness of a downloaded file.
+
+For the moment Ivy supports md5 and sha1 algorithm.
+
+The configuration of using md5 and/or sha1 can be done globally or by dependency resolver.
+Globally, use the ivy.checksums variable to list the check to be done (only md5 and sha1 are supported).
+On each resolver you can use the checksums attribute to override the global setting.
+
+The setting is a comma separated list of checksum algorithm to use.
+During checking (at download time), the first checksum found is checked, and that's all. This means that if you have a "sha1, md5" setting, then if ivy finds a sha1 file, it will compare the downloaded file sha1 against this sha1, and if the comparison is ok, it will assume the file is ok. If no sha1 file is found, it will look for a md5 file. If none is found no checking is done.
+During publish, all listed checksum algorithms are computed and uploaded.
+
+By default checksum algorithms are "sha1, md5".
+<h2><a href="../../doc/configuration/resolvers#common.html">Fail when no module descriptor is found</a></h2>
+By default when ivy doesn't find a module descriptor for a module, it lloks for an artifact, and if it finds one it assumes a default module descriptor. 
+It is now possible to configure this behaviour per resolver, by setting the allownomd attribute to false you can force the use of a module descriptor, and fail if none is found. This is also useful to improve performances on a resolver for which you know you will always have module descriptors.
+<h2>System properties</h2>
+All java system properties are now available as ivy variables in your configuration files.
+Thus you can now easily define the default cache relative to user home (using ${user.home}), or access any specific property set via the standard java system property mechanism.
+
+<h2><a href="../../doc/configuration/resolvers#common.html">Changing pattern</a></h2>
+You can now define a changingPattern and a changingMatcher to configure a set of revisions which should always be considered as changing one (artifacts are checked to see if they are up to date).
+
+The pattern and the matcher name are attributes available on all built-in resolvers.
+
+Example:
+<code type="xml">
+<filesystem name="local" changingPattern="*-SNAPSHOT" changingMatcher="glob">
+</code>
+will consider all modules with a revision ending by SNAPSHOT to be changing revisions.
+
+<h2><a href="../../doc/configuration/classpath.html">Customisable classpath</a></h2>
+You can now add jars to use to load plugins directly in ivy configuration, so that you can easily use your plugins in several execution environment (ant, standalone, IDE plugin, ...).
+
+Example:
+<code type="xml">
+<ivyconf>
+  <classpath file="${ivy.settings.dir}/custom-resolver.jar"/>
+  <typedef name="custom" classname="fr.jayasoft.ivy.resolver.CustomResolver"/>
+  <resolvers>
+    <custom name="custom"/>
+  </resolvers>
+</ivyconf>
+</code>
+
+<h1>Ant tasks</h1>
+<h2><a href="../../doc/use/repreport.html">repreport</a></h2>
+A new repreport task allows to generate reports directly from your repository. The graph generation is the most interesting one, it can gives you a good overview of the dependencies between of all your modules available in your repository, or restrict this graph to just the modules from this organisation, and so on.
+
+Example:
+<code type="xml">
+<ivy:repreport organisation="myorg" xml="false" graph="true" />
+will generate a graphml of dependencies with all modules in the organisation "myorg"
+</code>
+
+<h2><a href="../../doc/use/artifactreport.html">artifactreport</a></h2>
+A new artifactreport task has been introduced to easily generate an xml report with artifacts resolved, with useful information such as their original location. This report is particularly well suited for generating IDE classpaths (see also the <a href="../../links.html">links</a> page for higher IDE integration via plugins).
+
+The generated report looks like this:
+<code type="xml">
+<?xml version="1.0" encoding="UTF-8"?>
+<modules>
+  <module organisation="hippo" name="sant-classes" rev="1.01.00b04-dev" status="integration">
+    <artifact name="sant-classes-src" ext="zip" type="zip">
+      <origin-location is-local="true">
+        C:/home/jstuyts/data/ivy/local/hippo/sant-classes/1.01.00b04-dev/sant-classes-src-1.01.00b04-dev.zip</origin-location>
+      <cache-location>
+        C:/home/jstuyts/data/ivy/cache/hippo/sant-classes/zips/sant-classes-src-1.01.00b04-dev.zip</cache-location>
+      <retrieve-location>lib/test/sant-classes-src-1.01.00b04-dev.zip</retrieve-location>
+    </artifact>
+  </module>
+  <module organisation="testng" name="testng" rev="4.6.1-jdk15" status="release">
+    <artifact name="testng" ext="jar" type="jar">
+      <origin-location is-local="false">
+        http://repository.hippocms.org/maven/testng/jars/testng-4.6.1-jdk15.jar</origin-location>
+      <cache-location>C:/home/jstuyts/data/ivy/cache/testng/testng/jars/testng-4.6.1-jdk15.jar</cache-location>
+      <retrieve-location>lib/test/testng-4.6.1-jdk15.jar</retrieve-location>
+    </artifact>
+  </module>
+</code>
+
+<h2><a href="../../doc/use/info.html">info</a></h2>
+The new info task eases the access to some essential data contained in an ivy file without performing a dependency resolution.
+
+Example:
+<code type="xml">
+<ivy:info file="${basedir}/path/to/ivy.xml" />
+</code>
+
+<h2><a href="../../doc/use/listmodules.html">listmodules</a></h2>
+The new listmodules task let you list modules available in the repository and set ant properties accordingly.
+
+Example:
+<code type="xml">
+<ivy:listmodules organisation="jayasoft" module="ivy" revision="*" property="ivy.[revision]" value=="found"/>
+</code>
+
+<h2><a href="../../doc/use/findrevision.html">findrevision</a></h2>
+This new task sets an ant property with the latest revision found for a given module matching a given revision constraint.
+
+<code type="xml">
+<ivy:findrevision organisation="jayasoft" module="ivy" revision="1.0+"/>
+</code>
+
+<h2><a href="../../doc/use/resolve.html">useOrigin</a></h2>
+The resolve, cachepath, and retrieve tasks now supports a new useOrigin attribute, which allow to use the original location of local artifacts instead of their location in ivy cache. Used directly on a resolve or when no resolve has been done, it will avoid the copy of the artifact to the cache, and use directly the artifact from its original location.
+
+<code type="xml">
+<cachepath pathid="default.classpath" conf="default" useOrigin="true" />
+</code>
+<h2><a href="../../doc/use/resolve.html">Disable transitive dependencies on resolve</a></h2>
+You can now disable transitive dependencies on resolve.
+
+Example:
+<code type="xml">
+<ivy:resolve file="path/to/ivy.xml" transitive="false" />
+</code>
+<h2><a href="../../doc/use/retrieve.html">Synchronization feature in retrieve</a></h2>
+The retrieve task can now performs a real synchronization of the destination directory, instead of a simple copy.
+
+Example:
+<code type="xml">
+<ivy:retrieve pattern="${lib.dir}/[conf]/[artifact].[ext]" sync="true" />
+</code>
+
+<h1>Standalone mode</h1>
+<h2>Application launcher</h2>
+Ivy can now be used as an application launcher:
+<code>
+java fr.jayasoft.ivy.Main -conf path/to/myivyconf.xml -dependency bar foo 2.0 -main org.bar.foo.FooMain
+</code>
+calls ivy with given ivyconf file and resolve bar foo 2.0, and then run org.foo.FooMain class with the resolved artifacts (foo 2.0 and its dependencies) as classpath
+</div>
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

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

Modified: incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.0-alpha-1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.0-alpha-1.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.0-alpha-1.html (original)
+++ incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.0-alpha-1.html Wed May  9 03:58:10 2007
@@ -1,29 +1,29 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
 	<textarea id="xooki-source">
 <h2>Disclaimer</h2>
 <code>
@@ -224,7 +224,7 @@
 - FIX: Comments in ivy.xml duplicated (IVY-336) (thanks to Gilles Scokart)
 - FIX: Ivy failure when the ivy.xml file contains non US-ASCII characters (IVY-346) (thanks to Gilles Scokart)
 - FIX: Urlresolver is not possible to use dynamic revisions on nonstandard repository structure (IVY-350) (thanks to Pierre H├Ągnestrand)
-</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Propchange: incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.0-alpha-1.html
------------------------------------------------------------------------------
    svn:eol-style = LF

Modified: incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.html (original)
+++ incubator/ivy/core/trunk/doc/doc/releasenotes/2.0.html Wed May  9 03:58:10 2007
@@ -1,35 +1,35 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
 	<textarea id="xooki-source">
 The 2.0 version will be the first stable version released at Apache.
 
 Most of the efforts of the development team is concentrated on this version, and a [[doc/releasenotes/2.0.0-alpha-1 first alpha]] version is available for early preview.
 
-Despite the version name, the 2.0 version will be mostly backward compatible with prior 1.x versions. Indeed we choose to use a major version number change to reflect the change in the Ivy API which has been deeply revisited, and our migration to the Apache Software Foundation. But from a user point of view, Ivy 2.0 will be mostly a drop in replacement of the previous 1.x versions.</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+Despite the version name, the 2.0 version will be mostly backward compatible with prior 1.x versions. Indeed we choose to use a major version number change to reflect the change in the Ivy API which has been deeply revisited, and our migration to the Apache Software Foundation. But from a user point of view, Ivy 2.0 will be mostly a drop in replacement of the previous 1.x versions.</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

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

Modified: incubator/ivy/core/trunk/doc/doc/resolver/chain.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/chain.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/chain.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/chain.html Wed May  9 03:58:10 2007
@@ -1,94 +1,94 @@
-<!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">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">chain</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">depends on sub resolvers</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">delegates to first sub resolver in chain</td></tr>
-</table>
-
-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.
-<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>returnFirst</td><td>true if the first found should be returned.</td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>dual</td><td>true if the chain should behave like a dual chain. <span class="since">since 1.3</span></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>any resolver</td><td>a sub resolver to use</td>
-        <td>1..n</td></tr>
-</tbody>
-</table>
-<h1>Examples</h1>
-<code type="xml">
-<chain name="test">
-  <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>
-  <ivyrep name="2"/>
-</chain>
-</code>
-Both a filesystem and ivyrep will be used to look for ivy files. If a dynamic revision is required, then both the filesystem and ivyrep will be queried to find the most recent revision among the two resolvers. Once the most recent revision is found in one resolver, it's the same resolver which will be used to download artifacts.
-<hr/>
-<code type="xml">
-<chain name="test" returnFirst="true">
-  <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>
-  <ivyrep name="2"/>
-</chain>
-</code>
-Same as before, except that if a revision is found in the filesystem then ivyrep will not be queried: its the filesystem which will be used for both the ivy file and the artifacts.
-<hr/>
-<code type="xml">
-<chain name="test" dual="true">
-  <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>
-  <ivyrep name="2"/>
-</chain>
-</code>
-Same as first example, except that once a module is found by either filesystem or ivyrep, then it's the whole chain which will be queried to download the artifacts. So in this case ivy file and artifacts may be split across the two resolvers for the same module.
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">chain</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">depends on sub resolvers</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">delegates to first sub resolver in chain</td></tr>
+</table>
+
+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.
+<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>returnFirst</td><td>true if the first found should be returned.</td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>dual</td><td>true if the chain should behave like a dual chain. <span class="since">since 1.3</span></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>any resolver</td><td>a sub resolver to use</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<chain name="test">
+  <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>
+  <ivyrep name="2"/>
+</chain>
+</code>
+Both a filesystem and ivyrep will be used to look for ivy files. If a dynamic revision is required, then both the filesystem and ivyrep will be queried to find the most recent revision among the two resolvers. Once the most recent revision is found in one resolver, it's the same resolver which will be used to download artifacts.
+<hr/>
+<code type="xml">
+<chain name="test" returnFirst="true">
+  <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>
+  <ivyrep name="2"/>
+</chain>
+</code>
+Same as before, except that if a revision is found in the filesystem then ivyrep will not be queried: its the filesystem which will be used for both the ivy file and the artifacts.
+<hr/>
+<code type="xml">
+<chain name="test" dual="true">
+  <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>
+  <ivyrep name="2"/>
+</chain>
+</code>
+Same as first example, except that once a module is found by either filesystem or ivyrep, then it's the whole chain which will be queried to download the artifacts. So in this case ivy file and artifacts may be split across the two resolvers for the same module.
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

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

Modified: incubator/ivy/core/trunk/doc/doc/resolver/dual.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/dual.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/dual.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/dual.html Wed May  9 03:58:10 2007
@@ -1,62 +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: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">dual</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">depends on sub resolvers</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">delegates to ivy sub resolver if artifact to publish is of "ivy" type, to artifact sub resolver otherwise</td></tr>
-</table>
-
-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.
-<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>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>
-    </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>any resolver</td><td>two resolvers, the first being the ivy resolver, the second the artifact resolver</td>
-        <td>2</td></tr>
-</tbody>
-</table>
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">dual</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">depends on sub resolvers</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">delegates to ivy sub resolver if artifact to publish is of "ivy" type, to artifact sub resolver otherwise</td></tr>
+</table>
+
+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.
+<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>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>
+    </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>any resolver</td><td>two resolvers, the first being the ivy resolver, the second the artifact resolver</td>
+        <td>2</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

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

Modified: incubator/ivy/core/trunk/doc/doc/resolver/filesystem.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/filesystem.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/filesystem.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/filesystem.html Wed May  9 03:58:10 2007
@@ -1,69 +1,69 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<!--
-   Licensed to the Apache Software Foundation (ASF) under one
-   or more contributor license agreements.  See the NOTICE file
-   distributed with this work for additional information
-   regarding copyright ownership.  The ASF licenses this file
-   to you under the Apache License, Version 2.0 (the
-   "License"); you may not use this file except in compliance
-   with the License.  You may obtain a copy of the License at
-
-     http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing,
-   software distributed under the License is distributed on an
-   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-   KIND, either express or implied.  See the License for the
-   specific language governing permissions and limitations
-   under the License.    
--->
-<html>
-<head>
-	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
-	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
-	<script type="text/javascript" src="../../xooki/xooki.js"></script>
-</head>
-<body>
-	<textarea id="xooki-source">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">filesystem</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">yes</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">yes</td></tr>
-</table><br/>
-
-This resolver uses the file system to resolve ivy files and artifacts. It presents the advantage to usually have very good performances. Moreover, it is easy to setup using basic OS file sharing mechanism.
-
-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.
-
-<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/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>
-</thead>
-<tbody>
-    <tr><td>m2compatible</td><td>True if this resolver should be maven2 compatible, false otherwise <span class="since">since 1.3</span></td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>local</td><td>True if this resolver should be considered local, false otherwise <span class="since">since 1.4</span>. See useOrigin attribute on the [[ant:resolve]] task for details.</td>
-        <td>No, defaults to true</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>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
-        <td>0..n</td></tr>
-    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
-        <td>1..n</td></tr>
-</tbody>
-</table>
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">filesystem</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">yes</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">yes</td></tr>
+</table><br/>
+
+This resolver uses the file system to resolve ivy files and artifacts. It presents the advantage to usually have very good performances. Moreover, it is easy to setup using basic OS file sharing mechanism.
+
+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.
+
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/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>
+</thead>
+<tbody>
+    <tr><td>m2compatible</td><td>True if this resolver should be maven2 compatible, false otherwise <span class="since">since 1.3</span></td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>local</td><td>True if this resolver should be considered local, false otherwise <span class="since">since 1.4</span>. See useOrigin attribute on the [[ant:resolve]] task for details.</td>
+        <td>No, defaults to true</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>ivy</td><td>defines a pattern for ivy files, using the pattern attribute</td>
+        <td>0..n</td></tr>
+    <tr><td>artifact</td><td>defines a pattern for artifacts, using the pattern attribute</td>
+        <td>1..n</td></tr>
+</tbody>
+</table>
+
+	</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

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

Modified: incubator/ivy/core/trunk/doc/doc/resolver/ibiblio.html
URL: http://svn.apache.org/viewvc/incubator/ivy/core/trunk/doc/doc/resolver/ibiblio.html?view=diff&rev=536488&r1=536487&r2=536488
==============================================================================
--- incubator/ivy/core/trunk/doc/doc/resolver/ibiblio.html (original)
+++ incubator/ivy/core/trunk/doc/doc/resolver/ibiblio.html Wed May  9 03:58:10 2007
@@ -1,68 +1,68 @@
-<!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">
-<table class="resolver">
-<tr><td class="title">Tag</td><td class="value">ibiblio</td></tr>
-<tr><td class="title">Handle latest</td><td class="value">yes, at least if the repository server is apache based</td></tr>
-<tr><td class="title">Handle publish</td><td class="value">no</td></tr>
-</table>
-
-This resolver usually uses ibiblio to find artifacts. 
-
-Prefer the use of ivyrep resolver which adds ivy file handling to this resolver.
-
-<span class="since">since 1.3</span> Using the m2compatible attribute, you can benefit from maven 2 repository compatibility (convert dots in organisation in slashes, search for poms, use transitive dependencies of poms). This setting also affects the default place where the resolver look for its artifacts to point to the maven2 repository. So setting this attribute to true is sufficient to use maven 2 ibiblio repository.
-
-<span class="since">since 1.4</span> When using the m2compatible flag, you can disable the use of poms by setting the usepoms flag to false. It is then roughly equivalent to an url resolver configured like this:
-<code type="xml">
-<url name="test" m2compatible="true">
-  <artifact pattern="http://www.ibiblio.org/maven2/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
-</url>
-</code>
-
-<h1>Attributes</h1>
-This resolver shares the <a href="../../doc/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>
-</thead>
-<tbody>
-    <tr><td>root</td><td>the root of the artifacts repository.</td>
-        <td>No, defaults to ${ivy.ibiblio.default.artifact.root}</td></tr>
-    <tr><td>pattern</td><td>a pattern describing the layout of the artifacts repository.</td>
-        <td>No, defaults to ${ivy.ibiblio.default.artifact.pattern}</td></tr>
-    <tr><td>m2compatible</td><td>True if this resolver should be maven2 compatible, false otherwise <span class="since">since 1.3</span></td>
-        <td>No, defaults to false</td></tr>
-    <tr><td>usepoms</td><td>True if this resolver should use maven poms when it is already in m2compatible mode, false otherwise <span class="since">since 1.4</span></td>
-        <td>No, defaults to true</td></tr>
-</tbody>
-</table>
-
-	</textarea>
-<script type="text/javascript">xooki.postProcess();</script>
-</body>
-</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+   Licensed to the Apache Software Foundation (ASF) under one
+   or more contributor license agreements.  See the NOTICE file
+   distributed with this work for additional information
+   regarding copyright ownership.  The ASF licenses this file
+   to you under the Apache License, Version 2.0 (the
+   "License"); you may not use this file except in compliance
+   with the License.  You may obtain a copy of the License at
+
+     http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing,
+   software distributed under the License is distributed on an
+   "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+   KIND, either express or implied.  See the License for the
+   specific language governing permissions and limitations
+   under the License.    
+-->
+<html>
+<head>
+	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+	<script type="text/javascript">var xookiConfig = {level: 2};</script>	
+	<script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table class="resolver">
+<tr><td class="title">Tag</td><td class="value">ibiblio</td></tr>
+<tr><td class="title">Handle latest</td><td class="value">yes, at least if the repository server is apache based</td></tr>
+<tr><td class="title">Handle publish</td><td class="value">no</td></tr>
+</table>
+
+This resolver usually uses ibiblio to find artifacts. 
+
+Prefer the use of ivyrep resolver which adds ivy file handling to this resolver.
+
+<span class="since">since 1.3</span> Using the m2compatible attribute, you can benefit from maven 2 repository compatibility (convert dots in organisation in slashes, search for poms, use transitive dependencies of poms). This setting also affects the default place where the resolver look for its artifacts to point to the maven2 repository. So setting this attribute to true is sufficient to use maven 2 ibiblio repository.
+
+<span class="since">since 1.4</span> When using the m2compatible flag, you can disable the use of poms by setting the usepoms flag to false. It is then roughly equivalent to an url resolver configured like this:
+<code type="xml">
+<url name="test" m2compatible="true">
+  <artifact pattern="http://www.ibiblio.org/maven2/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
+</url>
+</code>
+
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/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>
+</thead>
+<tbody>
+    <tr><td>root</td><td>the root of the artifacts repository.</td>
+        <td>No, defaults to ${ivy.ibiblio.default.artifact.root}</td></tr>
+    <tr><td>pattern</td><td>a pattern describing the layout of the artifacts repository.</td>
+        <td>No, defaults to ${ivy.ibiblio.default.artifact.pattern}</td></tr>
+    <tr><td>m2compatible</td><td>True if this resolver should be maven2 compatible, false otherwise <span class="since">since 1.3</span></td>
+        <td>No, defaults to false</td></tr>
+    <tr><td>usepoms</td><td>True if this resolver should use maven poms when it is already in m2compatible mode, false otherwise <span class="since">since 1.4</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/doc/resolver/ibiblio.html
------------------------------------------------------------------------------
    svn:eol-style = LF



Mime
View raw message