incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xav...@apache.org
Subject svn commit: r491923 [1/2] - in /incubator/ivy/trunk/src/doc/xooki: ./ doc/ images/ samples/ samples/multi-project/ style/
Date Tue, 02 Jan 2007 20:14:14 GMT
Author: xavier
Date: Tue Jan  2 12:14:12 2007
New Revision: 491923

URL: http://svn.apache.org/viewvc?view=rev&rev=491923
Log:
documentation and web site migration form old jayasoft site

Added:
    incubator/ivy/trunk/src/doc/xooki/choose-distrib.html
    incubator/ivy/trunk/src/doc/xooki/demo.html
    incubator/ivy/trunk/src/doc/xooki/download.html
    incubator/ivy/trunk/src/doc/xooki/faq.html
    incubator/ivy/trunk/src/doc/xooki/features.html
    incubator/ivy/trunk/src/doc/xooki/get-involved.html
    incubator/ivy/trunk/src/doc/xooki/images/hibgraph-small.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/hibgraph.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/ivy-book.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/ivy-demo.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/ivy-dl-1.4.1.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/ivy-forum.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/ivy-lierre.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/ivyfile-small.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/main-tasks.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/report-small.png   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step1.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step2.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step3-2.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step3.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step4.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step5.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step6.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/images/yed-step7.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/index.html
    incubator/ivy/trunk/src/doc/xooki/issues.html
    incubator/ivy/trunk/src/doc/xooki/license.html
    incubator/ivy/trunk/src/doc/xooki/links.html
    incubator/ivy/trunk/src/doc/xooki/mailing-lists.html
    incubator/ivy/trunk/src/doc/xooki/samples/
    incubator/ivy/trunk/src/doc/xooki/samples/build.xml
    incubator/ivy/trunk/src/doc/xooki/samples/commons-lang1.0-dep-report-part.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/samples/hibernate3.0-dep-report-part.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/samples/ivy-doc.xsl
    incubator/ivy/trunk/src/doc/xooki/samples/ivy-report.css
    incubator/ivy/trunk/src/doc/xooki/samples/ivy-sample-xslt.xml
    incubator/ivy/trunk/src/doc/xooki/samples/ivy-sample.xml
    incubator/ivy/trunk/src/doc/xooki/samples/ivy-style.css
    incubator/ivy/trunk/src/doc/xooki/samples/ivyconf-default.xml
    incubator/ivy/trunk/src/doc/xooki/samples/jayasoft-ivyrep-example-default.html
    incubator/ivy/trunk/src/doc/xooki/samples/jayasoft-ivyrep-example-default.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/samples/multi-project/
    incubator/ivy/trunk/src/doc/xooki/samples/multi-project/build.xml
    incubator/ivy/trunk/src/doc/xooki/samples/multi-project/common.xml
    incubator/ivy/trunk/src/doc/xooki/samples/projects-dependencies-graph-small.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/samples/projects-dependencies-graph.jpg   (with props)
    incubator/ivy/trunk/src/doc/xooki/testimonials.html
Modified:
    incubator/ivy/trunk/src/doc/xooki/doc.html
    incubator/ivy/trunk/src/doc/xooki/doc/extend.html
    incubator/ivy/trunk/src/doc/xooki/doc/principle.html
    incubator/ivy/trunk/src/doc/xooki/doc/tutorial.html
    incubator/ivy/trunk/src/doc/xooki/doc/yed.html
    incubator/ivy/trunk/src/doc/xooki/ivyrep.html
    incubator/ivy/trunk/src/doc/xooki/style/style.css
    incubator/ivy/trunk/src/doc/xooki/template.html
    incubator/ivy/trunk/src/doc/xooki/toc.json

Added: incubator/ivy/trunk/src/doc/xooki/choose-distrib.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/choose-distrib.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/choose-distrib.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/choose-distrib.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,22 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Each distribution of ivy contains samples. The documentation is packaged separately due to its size. It corresponds to a snapshot of the online documentation at the time of the release. Prefer the site itself if you want to have an updated and commented version of the documentation.
+With each version of ivy, you can find:
+<h2>binary distribution</h2>
+Containing ivy jars, dependencies and samples.
+This is the recommended version if you just want to use ivy. It requires at least a jre 1.4+ to run, and it is recommended to use it from ant (1.5.1+, 1.6.2+ recommended).
+<h2>sources</h2>
+Ready to be build with ant 1.6.0 or greater and ... ivy 1.4-RC1+. Yes, ivy eats its own dog food, and needs a binary version of itself to be build. Note that you will also need to have an internet access during build in order to ivy to download dependencies from ibiblio.
+This is the recommended version if you want to build ivy yourself and see it in action at the same time.
+<i>Note:</i> version 1.6.0 of ant is required here because the build file use its namespace feature to import ivy tasks.
+<h2>documentation</h2>
+Full ivy documentation easily browsable offline, packaged as a zip.</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/demo.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/demo.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/demo.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/demo.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,12 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+The Ivy demo is not available yet. Come back later or contribute a new demo!</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Modified: incubator/ivy/trunk/src/doc/xooki/doc.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc.html?view=diff&rev=491923&r1=491922&r2=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc.html (original)
+++ incubator/ivy/trunk/src/doc/xooki/doc.html Tue Jan  2 12:14:12 2007
@@ -5,41 +5,47 @@
 	<script type="text/javascript" src="xooki/xooki.js"></script>
 </head>
 <body>
-	<textarea id="xooki-source">
-Welcome to the official Ivy documentation.
-
-<h1>What is Ivy?</h1>
-Ivy is an agile dependency manager, primarily focused on managing java dependencies.
-Ivy is open source and released under a very permissive <a href="license.html">BSD license</a>.
-Ivy has a lot of powerful <a href="features.html">features</a>, the most popular and useful being its flexibily, integration with ant, and its strong transitive dependencies management engine.
-The transitive dependencies management is a feature which let you get dependencies of your dependencies, transitively. In order to address this problematic ivy needs to find metadata about your modules, usually in an <a href="doc/ivyfile.html">ivy file</a>. To find these metadata and your dependencies artifacts (usually jars), Ivy can be configured to use a lot of different <a href="doc/configuration/resolvers.html">repositories</a>.
-
-<h1>About this doc</h1>
-If you browse this documentation from your installation of ivy, you can also check the <a href="http://www.jayasoft.org/ivy/doc">online version</a> for latest updates and comments. To easily navigate to the online version, you will find a link to the corresponding online version on each page just after the title.
-
-The online version of this documentation is updated periodically, especially when new features are added during development. So if you find something documented here not available in your version of ivy, it may be because it is available only with the latest <a href="download.html">download</a>.
-
-If you want to view the whole documentation in a single printer-friendly page, please use the <a href="doc/print.html">printer-friendly link</a> at the bottom of any documentation page in the online documentation.
-
-<h1>Other places to go</h1>
-Check Ivy <a href="features.html">features</a>. 
-Read our <a href="faq.html">FAQ</a>.
-Ask for help on our <a href="forum.html">forum</a>.
-Report bug or feature request in our <a href="./issues">issue tracking system</a>.
-Check <a href="links.html">external tools and resources</a>.
-
-<h1>Overview</h1>
-This documentation is decomposed in 3 main parts:
-<ul>
-  <li><a href="doc/tutorial.html">Tutorials</a></li> 
-The tutorials is the best way to begin to play with ivy. You will easily and quickly learn the basics of Ivy.
-  <li><a href="doc/reference.html">Reference</a></li> 
-The reference documentation gives you all the details of Ivy. 
-The introduction part is particularly useful: it defines some vocabulary, explains main concepts such as dependency resolvers and patterns, and give an overview on how ivy works internally. 
-It's also in the reference doc that you will find all you always dreamed to know about ivy configuration, ivy files, and ivy use (especially with ant).
-  <li><a href="doc/appendix.html">Appendix</a></li> 
-The appendix section contains a bunch of Ivy related information which is not part of Ivy reference doc.
-</ul>
+	<textarea id="xooki-source">
+Welcome to the official Ivy documentation.
+
+<h1>What is Ivy?</h1>
+Ivy is an agile dependency manager, primarily focused on managing java dependencies.
+Ivy is open source and released under a very permissive <a href="license.html">license</a>.
+Ivy has a lot of powerful [[features]], the most popular and useful being its flexibily, integration with ant, and its strong transitive dependencies management engine.
+The transitive dependencies management is a feature which let you get dependencies of your dependencies, transitively. In order to address this problematic ivy needs to find metadata about your modules, usually in an <a href="doc/ivyfile.html">ivy file</a>. To find these metadata and your dependencies artifacts (usually jars), Ivy can be configured to use a lot of different <a href="doc/configuration/resolvers.html">repositories</a>.
+
+<h1>About this doc</h1>
+This documentation has been migrated from the old Ivy web site hosted by Jayasoft, feel free to report any problem on the [[mailing-lists]].
+
+If you browse this documentation from your installation of ivy, you can also check the <a href="http://www.jayasoft.org/ivy/doc">online version</a> for latest updates.
+
+You can also browse this documentation offline either by downloading the documentation distribution, or by checking out the src/doc directory from svn. This documentation uses <a href="http://xooki.sourceforge.net/">xooki</a> as documentation engine, so you can very easily [[get-involved edit it and submit patches]] when you browse it from source.
+
+The online version of this documentation is updated periodically, especially when new features are added during development. So if you find something documented here not available in your version of ivy, it may be because it is available only with the latest <a href="download.html">download</a>.
+
+If you want to view the whole documentation in a single printer-friendly page, please use the <a href="doc.html?action=print">printer-friendly link</a> at the bottom of any documentation page in the online documentation, and you will get a printer friendly version of the current page and all its sub pages.
+
+<h1>Other places to go</h1>
+Check Ivy <a href="features.html">features</a>. 
+Read our <a href="faq.html">FAQ</a>.
+Ask for help on our <a href="mailing-lists.html">mailing lists</a>.
+Report bug or feature request in our <a href="issues.html">issue tracking system</a>.
+Check <a href="links.html">external tools and resources</a>.
+
+<h1>Overview</h1>
+This documentation is decomposed in 3 main parts:
+<ul>
+  <li><a href="doc/tutorial.html">Tutorials</a></li> 
+The tutorials is the best way to begin to play with ivy. You will easily and quickly learn the basics of Ivy.
+  <li><a href="doc/reference.html">Reference</a></li> 
+The reference documentation gives you all the details of Ivy. 
+The introduction part is particularly useful: it defines some vocabulary, explains main concepts such as dependency resolvers and patterns, and give an overview on how ivy works internally. 
+It's also in the reference doc that you will find all you always dreamed to know about ivy configuration, ivy files, and ivy use (especially with ant).
+  <li><a href="doc/appendix.html">Appendix</a></li> 
+The appendix section contains a bunch of Ivy related information which is not part of Ivy reference doc.
+</ul>
+
+You will also find here interesting pages like [[doc/bestpractices]], the [[faq]] or the [[links]] pages.
 	</textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Modified: incubator/ivy/trunk/src/doc/xooki/doc/extend.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/extend.html?view=diff&rev=491923&r1=491922&r2=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/extend.html (original)
+++ incubator/ivy/trunk/src/doc/xooki/doc/extend.html Tue Jan  2 12:14:12 2007
@@ -5,47 +5,42 @@
 	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
-	<textarea id="xooki-source">
-Many things are configurable in ivy, and many things are available with ivy core. But when you want to do 
-something not built in ivy core, you can still plug your own code.<br/><br/>
-
-Several things are pluggable in ivy:
-<ul>
-<li>module descriptor parsers</li>
-<li>dependency resolvers</li>
-<li>latest strategies</li>
-<li>conflict managers</li>
-<li>report outputters</li>
-<li>version matchers</li>
-<li>triggers</li>
-</ul>
-
-Before trying to implement your own, we encourage you to check if the solution to your problem cannot be 
-addressed by existing features, or by <a href="../links.html">contributed ones</a>. Do not hesitate to ask for help on the forum.<br/><br/>
-
-If you still don't find what you need, there are two solutions:<br/>
-- prepare yourself to enter in ivy internals<br/>
-- <a href="mailto:commercial@jayasoft.org">contact us</a> to ask for specific development or advice. As ivy creators,
-we will always spend less time to implement your features or help you make good developement environment a reality.
-So do not hesitate to contact us and ask for a pricing.<br/><br/>
-
-And what if you still want to develop your own plugins ? Here are the main things to know...<br/><br/>
-
-All ivy plug-ins use the same code patterns as ant specific tasks for parameters. This means that
-if you want to have a "myattribute" of type String, you just have to declare a method called
-setMyattribute(String val) on your plug-in. The same applies to child tags, you just have to follow ant specifications.<br/><br/>
-
-Knowing that, you then have to implement the appropriate interface:
-<ul>
-<li>fr.jayasoft.ivy.DependencyResolver for dependency resolvers</li>
-<li>fr.jayasoft.ivy.LatestStrategy for latest strategies</li>
-<li>fr.jayasoft.ivy.ConflictManager for conflict managers</li>
-<li>fr.jayasoft.ivy.parser.ModuleDescriptorParser for module descriptor parsers</li>
-</ul>
-
-To help you understand what is required in each implementation, and what you can use to do it, have a look
-to existing implementations, it's the best advice we can give you !
-
+	<textarea id="xooki-source">
+Many things are configurable in ivy, and many things are available with ivy core. But when you want to do 
+something not built in ivy core, you can still plug your own code.<br/><br/>
+
+Several things are pluggable in ivy:
+<ul>
+<li>module descriptor parsers</li>
+<li>dependency resolvers</li>
+<li>latest strategies</li>
+<li>conflict managers</li>
+<li>report outputters</li>
+<li>version matchers</li>
+<li>triggers</li>
+</ul>
+
+Before trying to implement your own, we encourage you to check if the solution to your problem cannot be 
+addressed by existing features, or by <a href="../links.html">contributed ones</a>. Do not hesitate to ask for help on the [[mailing-lists]].<br/><br/>
+
+If you still don't find what you need, then you'll have to develop your own plugin or find someone who could do that for you.<br/><br/>
+
+Here are the main things to know if you want to develop your own plugins...<br/><br/>
+
+All ivy plug-ins use the same code patterns as ant specific tasks for parameters. This means that
+if you want to have a "myattribute" of type String, you just have to declare a method called
+setMyattribute(String val) on your plug-in. The same applies to child tags, you just have to follow ant specifications.<br/><br/>
+
+Knowing that, you then have to implement the appropriate interface:
+<ul>
+<li>fr.jayasoft.ivy.DependencyResolver for dependency resolvers</li>
+<li>fr.jayasoft.ivy.LatestStrategy for latest strategies</li>
+<li>fr.jayasoft.ivy.ConflictManager for conflict managers</li>
+<li>fr.jayasoft.ivy.parser.ModuleDescriptorParser for module descriptor parsers</li>
+</ul>
+
+To help you understand what is required in each implementation, and what you can use to do it, have a look to existing implementations, it's the best advice we can give you!
+
 	</textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Modified: incubator/ivy/trunk/src/doc/xooki/doc/principle.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/principle.html?view=diff&rev=491923&r1=491922&r2=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/principle.html (original)
+++ incubator/ivy/trunk/src/doc/xooki/doc/principle.html Tue Jan  2 12:14:12 2007
@@ -5,55 +5,55 @@
 	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
-	<textarea id="xooki-source">
-Now that you have been introduced to main ivy terminology and concepts, it is time to give some explanations about how ivy works.
-
-<h1>Usual cycle of modules between different locations</h1>
-<center><img src="/misc/ivy/images/main-tasks.png" /></center>
-More details on ant tasks <a href="../doc/use/ant.html">here</a>.
-
-<h1>Configure</h1>
-Ivy needs to be configured to be able to resolve your dependencies. This configuration is usually done with a configuration file, which defines a set of dependency resolvers. Each resolver is able to find ivy files and / or artifacts, given simple information such as organition, module, revision, artifact name, artifact type and artifact extension. 
-
-The configuration is also responsible for indicating which resolver should be used to resolve which module. This configuration is dependent only on your environment, i.e. where the modules and artifacts can be found. 
-
-A default configuration is used by ivy when none is given. This configuration uses ivyrep to resolve all modules.
-<h1>Resolve</h1>
-The resolve time is the moment when ivy actually resolve the dependencies of one module. It first needs to access the ivy file of the module for which it resolves the dependencies. 
-
-Then, for each dependency declared in this file, it asks the appropriate resolver (according to configuration) to find the module (i.e. either an ivy file for it, or its artifacts if no ivy file can be found). It also uses a filesystem based cache to avoid asking for a dependency if it is already in cache (at least if possible, which is not the case with latest revisions).
-
-If the resolver is a composite one (i.e. a chain or a dual resolver), several resolvers may actually be called to find the module.
-
-When the dependency module has been found, its ivy file is downloaded to ivy cache. Then ivy checks if it has itself dependencies, in which case it recursilvely traverse the graph of dependencies. 
-
-All over this traversal, conflict management are done to prevent the access to a module as soon as possible.
-
-When ivy has traversed the whole graph, it asks to the resolvers to download the artifacts corresponding to each dependencies which are not already in cache and which have not been evicted by conflict managers. All downloads are made to ivy cache.
-
-Finally, an xml report is generated in cache, which allows ivy to easily know what are all the dependencies of the module, without traversing the graph again.
-
-After this resolve step, two main steps are possible: either build a path with artifacts in cache, or copy them to another directory structure.
-
-<h1>Retrieve</h1>
-What is called retrieve in ivy is the fact to copy artifacts from the cache to another directory structure. This is done using a pattern, which indicates to ivy where the files should be copied.
-
-For this, ivy uses the xml report in cache corresponding to the module it should retrieve to know which artifacts should be copied.
-
-It also checks if the files are not already copied to maximize performances.
-<h1>Building a path from cache</h1>
-In some cases, it is preferable to use artifacts directly from the cache. Ivy is able to use the xml report generated at resolve time to build a path of all artifacts required.
-
-This can be particularly useful especially when building plug-ins for IDE.
-
-<h1>Reports</h1>
-Ivy is also able to generate readable reports describing the dependencies resolution.
-
-This is done with a simple xsl transformation of the xml report generated at resolve time.
-
-<h1>Publish</h1>
-Finally, Ivy can be used to publish a particular version of a module in your repository, so that it becomes available for futher resolve. This task is usually called either manually or from a continuous integration server for example.
-
+	<textarea id="xooki-source">
+Now that you have been introduced to main ivy terminology and concepts, it is time to give some explanations about how ivy works.
+
+<h1>Usual cycle of modules between different locations</h1>
+<center><img src="../images/main-tasks.png" /></center>
+More details on ant tasks <a href="../doc/use/ant.html">here</a>.
+
+<h1>Configure</h1>
+Ivy needs to be configured to be able to resolve your dependencies. This configuration is usually done with a configuration file, which defines a set of dependency resolvers. Each resolver is able to find ivy files and / or artifacts, given simple information such as organition, module, revision, artifact name, artifact type and artifact extension. 
+
+The configuration is also responsible for indicating which resolver should be used to resolve which module. This configuration is dependent only on your environment, i.e. where the modules and artifacts can be found. 
+
+A default configuration is used by ivy when none is given. This configuration uses ivyrep to resolve all modules.
+<h1>Resolve</h1>
+The resolve time is the moment when ivy actually resolve the dependencies of one module. It first needs to access the ivy file of the module for which it resolves the dependencies. 
+
+Then, for each dependency declared in this file, it asks the appropriate resolver (according to configuration) to find the module (i.e. either an ivy file for it, or its artifacts if no ivy file can be found). It also uses a filesystem based cache to avoid asking for a dependency if it is already in cache (at least if possible, which is not the case with latest revisions).
+
+If the resolver is a composite one (i.e. a chain or a dual resolver), several resolvers may actually be called to find the module.
+
+When the dependency module has been found, its ivy file is downloaded to ivy cache. Then ivy checks if it has itself dependencies, in which case it recursilvely traverse the graph of dependencies. 
+
+All over this traversal, conflict management are done to prevent the access to a module as soon as possible.
+
+When ivy has traversed the whole graph, it asks to the resolvers to download the artifacts corresponding to each dependencies which are not already in cache and which have not been evicted by conflict managers. All downloads are made to ivy cache.
+
+Finally, an xml report is generated in cache, which allows ivy to easily know what are all the dependencies of the module, without traversing the graph again.
+
+After this resolve step, two main steps are possible: either build a path with artifacts in cache, or copy them to another directory structure.
+
+<h1>Retrieve</h1>
+What is called retrieve in ivy is the fact to copy artifacts from the cache to another directory structure. This is done using a pattern, which indicates to ivy where the files should be copied.
+
+For this, ivy uses the xml report in cache corresponding to the module it should retrieve to know which artifacts should be copied.
+
+It also checks if the files are not already copied to maximize performances.
+<h1>Building a path from cache</h1>
+In some cases, it is preferable to use artifacts directly from the cache. Ivy is able to use the xml report generated at resolve time to build a path of all artifacts required.
+
+This can be particularly useful especially when building plug-ins for IDE.
+
+<h1>Reports</h1>
+Ivy is also able to generate readable reports describing the dependencies resolution.
+
+This is done with a simple xsl transformation of the xml report generated at resolve time.
+
+<h1>Publish</h1>
+Finally, Ivy can be used to publish a particular version of a module in your repository, so that it becomes available for futher resolve. This task is usually called either manually or from a continuous integration server for example.
+
 	</textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Modified: incubator/ivy/trunk/src/doc/xooki/doc/tutorial.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/tutorial.html?view=diff&rev=491923&r1=491922&r2=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/tutorial.html (original)
+++ incubator/ivy/trunk/src/doc/xooki/doc/tutorial.html Tue Jan  2 12:14:12 2007
@@ -5,38 +5,38 @@
 	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
-	<textarea id="xooki-source">
-The best way to learn is to practice! That's what the ivy tutorials will help you to do, to discover some of the great ivy <a href="../features.html">features</a>.
-
-Here is the very first tutorial, it doesn't even require to install Ivy, and should not take more than 30 seconds if you already have ant and a jdk properly installed:
-<ul>
-<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 <a href="http://svn.jayasoft.org/projects/tools/ivy/src/example/go-ivy/build.xml">this build file</a> 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>
-</ul>
-If you have any trouble, check the <a href="../faq.html">FAQ</a>, it may be related to your internet connection (proxy anyone?).
-
-OK, you've seen how easy it is to make your first step with ivy? Go ahead with the other tutorials, but before make sure you have properly <a href="../doc/install.html">installed</a> ivy and downloaded the tutorials sources (included in all ivy distributions, in the src/example directory).
-
-The following tutorials are available:
-<ul>
-<li><a href="../doc/tutorial/start.html">Quick Start</a></li> 
-guide you through your very first steps with ivy.
-<li><a href="../doc/tutorial/ivyrep.html">Using IvyRep</a></li> 
-show you the out of the box power of ivy + ivyrep.
-<li><a href="../doc/tutorial/defaultconf.html">Configuring default resolver</a></li> 
-give you a better understanding of the default configuration and show you how to customize it to your needs.
-<li><a href="../doc/tutorial/multiple.html">Multiple Resolvers</a></li> 
-teach you how to configure Ivy to find its dependencies in multiple places.
-<li><a href="../doc/tutorial/dual.html">Dual Resolver</a></li> 
-help you configure ivy to find ivy files in one place and artifacts in another.
-<li><a href="../doc/tutorial/multi-project.html">Project Dependencies</a></li> 
-makes you touch the interest of using ivy in multi project environment.
-<li><a href="../doc/tutorial/conf.html">Using Ivy Configurations</a></li> 
-show how to use configurations in ivy file to define set of artifacts.
-<li><a href="../doc/tutorial/build-repository.html">Building a repository</a></li> 
-show how to build your own enterprise repository.
-</ul>
+	<textarea id="xooki-source">
+The best way to learn is to practice! That's what the ivy tutorials will help you to do, to discover some of the great ivy <a href="../features.html">features</a>.
+
+Here is the very first tutorial, it doesn't even require to install Ivy, and should not take more than 30 seconds if you already have ant and a jdk properly installed:
+<ul>
+<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 <a href="../samples/build.xml">this build file</a> 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>
+</ul>
+If you have any trouble, check the <a href="../faq.html">FAQ</a>, it may be related to your internet connection (proxy anyone?).
+
+OK, you've seen how easy it is to make your first step with ivy? Go ahead with the other tutorials, but before make sure you have properly <a href="install.html">installed</a> ivy and downloaded the tutorials sources (included in all ivy distributions, in the src/example directory).
+
+The following tutorials are available:
+<ul>
+<li><a href="tutorial/start.html">Quick Start</a></li> 
+guide you through your very first steps with ivy.
+<li><a href="tutorial/ivyrep.html">Using IvyRep</a></li> 
+show you the out of the box power of ivy + ivyrep.
+<li><a href="tutorial/defaultconf.html">Configuring default resolver</a></li> 
+give you a better understanding of the default configuration and show you how to customize it to your needs.
+<li><a href="tutorial/multiple.html">Multiple Resolvers</a></li> 
+teach you how to configure Ivy to find its dependencies in multiple places.
+<li><a href="tutorial/dual.html">Dual Resolver</a></li> 
+help you configure ivy to find ivy files in one place and artifacts in another.
+<li><a href="tutorial/multi-project.html">Project Dependencies</a></li> 
+makes you touch the interest of using ivy in multi project environment.
+<li><a href="tutorial/conf.html">Using Ivy Configurations</a></li> 
+show how to use configurations in ivy file to define set of artifacts.
+<li><a href="tutorial/build-repository.html">Building a repository</a></li> 
+show how to build your own enterprise repository.
+</ul>
 	</textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Modified: incubator/ivy/trunk/src/doc/xooki/doc/yed.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/yed.html?view=diff&rev=491923&r1=491922&r2=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/yed.html (original)
+++ incubator/ivy/trunk/src/doc/xooki/doc/yed.html Tue Jan  2 12:14:12 2007
@@ -5,45 +5,43 @@
 	<script type="text/javascript" src="../xooki/xooki.js"></script>
 </head>
 <body>
-	<textarea id="xooki-source">
-<a href="http://www.yworks.com/en/products_yed_about.htm">yEd</a> is a free graph editor, benefiting from
-all the automatic layouts of yFiles. Ivy is able to generate graphs which are readable by yEd.<br/><br/>
-
-The graphs generated by ivy are not layed out (in fact it's why we use yEd), so you have to follow a simple
-sequence of steps to layout the generated graphs.<br/><br/>
-
-<h2>Preparation</h2>
-First you have to generate a graphml file. Simply call the report task (see <a href="../doc/use.html">ivy use documentation</a>)
-for that.
-
-<h2>Step 1: open the graphml file</h2>
-Launch yEd editor, and open the graphml file generated by the report task. You should obtain something like this:<br/>
-<center>
-<img src="/misc/ivy/images/yed-step1.JPG"/>
-</center>
-
-<h2>Step 2: ask yEd to adjust nodes size</h2>
-<center>
-<img src="/misc/ivy/images/yed-step2.JPG"/><br/>
-<img src="/misc/ivy/images/yed-step3.JPG"/><br/>
-<img src="/misc/ivy/images/yed-step3-2.JPG"/>
-</center>
-
-<h2>Step 3: ask yEd to layout nodes</h2>
-<center>
-<img src="/misc/ivy/images/yed-step4.JPG"/><br/>
-<img src="/misc/ivy/images/yed-step5.JPG"/><br/>
-<img src="/misc/ivy/images/yed-step6.JPG"/><br/>
-<br/>
-That's all, you should have obtained something like this:<br/><br/>
-<img src="/misc/ivy/images/yed-step7.JPG"/><br/>
-<br/>
-Note that this is only one possibility, test the available layouts yourself, you could find one better in your case.
-Once you have layed out the graph, you can either save it with in the same file (but be warned that it will be overwritten at next 
-ivy report call), or another file, export it to jpg, gif, svg, etc. (see <a href="http://www.yworks.com/en/products_yed_about.htm">yEd</a> site for details).
-</center>
-
-
+	<textarea id="xooki-source">
+<a href="http://www.yworks.com/en/products_yed_about.htm">yEd</a> is a free graph editor, benefiting from
+all the automatic layouts of yFiles. Ivy is able to generate graphs which are readable by yEd.
+
+The graphs generated by ivy are not layed out (in fact it's why we use yEd), so you have to follow a simple sequence of steps to layout the generated graphs.
+
+<h2>Preparation</h2>
+First you have to generate a graphml file. Simply call the report task (see <a href="../doc/use.html">ivy use documentation</a>) for that.
+
+<h2>Step 1: open the graphml file</h2>
+Launch yEd editor, and open the graphml file generated by the report task. You should obtain something like this:
+<center>
+<img src="../images/yed-step1.JPG"/><br/>
+</center>
+
+<h2>Step 2: ask yEd to adjust nodes size</h2>
+<center>
+<img src="../images/yed-step2.JPG"/><br/>
+<img src="../images/yed-step3.JPG"/><br/>
+<img src="../images/yed-step3-2.JPG"/><br/>
+</center>
+
+<h2>Step 3: ask yEd to layout nodes</h2>
+<center>
+<img src="../images/yed-step4.JPG"/><br/>
+<img src="../images/yed-step5.JPG"/><br/>
+<img src="../images/yed-step6.JPG"/><br/>
+
+That's all, you should have obtained something like this:
+
+<img src="../images/yed-step7.JPG"/><br/>
+
+Note that this is only one possibility, test the available layouts yourself, you could find one better in your case.
+Once you have layed out the graph, you can either save it with in the same file (but be warned that it will be overwritten at next ivy report call), or another file, export it to jpg, gif, svg, etc. (see <a href="http://www.yworks.com/en/products_yed_about.htm">yEd</a> site for details).
+</center>
+
+
 	</textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Added: incubator/ivy/trunk/src/doc/xooki/download.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/download.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/download.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/download.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,31 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Ivy has not yet released a version under the Apache Incubator. Previous releases can be considered production quality, but are not endorsed by the Apache Software Foundation.
+
+The latest stable version of Ivy is <a href="doc/releasenotes/1.4.1.html">1.4.1</a>, and is not an Apache incubating release, but a release done whlie hosted by jayasoft:
+<ul>
+<li><a href="http://www.jaya.free.fr/downloads/ivy/1.4.1/ivy-1.4.1-bin.zip">binaries</a></li>
+<li><a href="http://www.jaya.free.fr/downloads/ivy/1.4.1/ivy-1.4.1-src.zip">sources</a></li>
+<li><a href="http://www.jaya.free.fr/downloads/ivy/1.4.1/ivy-1.4.1-doc.zip">documentation</a></li>
+</ul>
+
+To have a quick overview of some of the changes in this version, check the <a href="doc/releasenotes/1.4.html">1.4.1 release notes</a> page.
+
+You can also download ivy jar and ivy.xml alone directly from the jayasoft site (useful especially for easy ant setup) using the following pattern:
+http://www.jayasoft.org/downloads/ivy/[revision]/[artifact]-[revision].[ext]
+
+This is used to auto install Ivy from internet, in the <a href="doc/tutorial.html">first tutorial</a>. Take a look at these examples if you want such an auto install feature in your own builds.
+The xsd for ivy files of the version is also available online at:
+http://www.jayasoft.org/downloads/ivy/[revision]/ivy.xsd
+
+To have info about the different kind of distributions, see <a href="choose-distrib.html">that page</a>.
+For previous version information and download, see the <a href="doc/releasenotes.html">release notes page</a> in the documentation.</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/faq.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/faq.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/faq.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/faq.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<h1>What and Why</h1>
+<h2>What is Ivy ?</h2>
+<p>Ivy is a powerful dependencies manager with transitive dependencies support and much more <a href="features.html">features</a>.</p>
+<p>With Ivy you define the dependencies of your module in an xml file, called an ivy file. Then you usually ask ivy to retrieve your dependencies to a local lib dir, and it does it for you by locating the artifacts of your dependencies in repositories, such as ibiblio.</p>
+<h2>Why should I use a dependencies manager ?</h2>
+<p>Without a dependencies manager, two solutions are often used to store the dependencies of a project: a project lib dir or direct access to a shared repository.<br />
+The major drawback of the project lib dir is that the same dependencies are stored in multiple location if you have several projects using the same dependencies. Moreover, we often see project where dependencies revisions are not documented, which can cause problems for maintenance.<br />
+With the shared repository the problem is often to maintain the list of dependencies of the project. This list is often lost within the build file, which does not help maintenance. Moreover, this solution often requires a download of the whole repository, unless home made dependencies management solution has been used.</p>
+<p>Finally, the major drawback of these solutions is that they do not use transitive dependencies. Transitive dependencies are the dependencies of your dependencies. Managing transitive dependencies  let you declare dependencies only on what you really need, and not what the module you use themselves need. This not only eases your dependencies declaration, but it also improves a lot the maintenability of your project, especially in multi-project environment. Imagine you develop a component used in several other projects. Then each time your component needs a new dependency, without transitive dependencies, you have to update all the projects using your component ! And this could really take a lot of time !</p>
+<h2>Why should I use Ivy ?</h2>
+<p>If you are convinced of using a dependencies manager, you may wonder why using Ivy and not another tool. We are not able to answer this question without being biased, but have a look at Ivy <a href="features.html">features</a> and the <a href="../search/node/ivy+doc+comparison.html">product comparison</a> we provide, and you will certainly see that Ivy is one of the best dependencies manager currently available ;-)</p>
+<h2>How does Ivy differ from Maven2 ?</h2>
+<p>The answer to this question is too long, so it deserves its own page <a href="doc/m2comparison.html">here</a>.</p>
+<h1>Ivy in use</h1>
+<h2>I don't understand what's happening...</h2>
+<p>The first thing to do when you don't understand what's going wrong is to try to change the message level. If you use ant, you can use the -debug or -verbose options to get more detailed messages and better understand what's happening.</p>
+<h2>Ivy seems to fail connecting to ibiblio...</h2>
+<p>First, check if the ibiblio site is ok with your favorite browser. If the site is ok, maybe it's a problem of proxy configuration. Set your ANT_OPTS environment variable<br />
+to configure your proxy if you have one.<br />
+For instance:<br />
+<code>set ANT_OPTS=-Dhttp.proxyHost=myproxy -Dhttp.proxyPort=3128</code></p>
+<p>If it still doesn't work, maybe it's your dependency file which is not ok. Check<br />
+if the module name you depend on is actually a name of directory under<br />
+<a href="http://www.ibiblio.org/maven/" title="www.ibiblio.org/maven/">www.ibiblio.org/maven/</a>. If this is the case, check if the jar with a name like<br />
+[module]-[revision].jar is present under the jars directory of this module on ibiblio.<br />
+For instance: <a href="http://www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.jar" title="www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.jar">www.ibiblio.org/maven/commons-httpclient/jars/commons-httpclient-2.0.jar</a></p>
+<p>If this is the case, check your ivy configuration to see if you actually use the ibiblio<br />
+or ivyrep resolver.</p>
+<p>Finally, you can check if the files were not downloaded but corrupted<br />
+(Ivy has no md5 checking for the moment) by checking your lib directory and opening<br />
+the jars if any with an unzip program.</p>
+<p>If you still have problems post on the <a href="forum/core.html">forum</a><br />
+mentioning your OS, your version of ant, your version of ivy, your configuration file<br />
+and your ivy file.</p>
+<h2>Ivy fails to get an artifact / ivy file on my http server. What's wrong?</h2>
+<p>The first thing to do is to ensure the setting is correct. Ivy should log the url it tried, copy this url and paste it in your favorite browser, and verify you get no error.</p>
+<p>If this is ok, check if you don't need any proxy setting nor authentication. For proxy setting, you can use for instance this:<br />
+<code>set ANT_OPTS=-Dhttp.proxyHost=myproxy -Dhttp.proxyPort=3128</code><br />
+For authentication, fill in the appropriate data at <a href="doc/use/configure.html">configuration</a> time.</p>
+<p>If you still have no idea of what is wrong, then I suggest to use commons-httpclient if it isn't already the case (you should just put commons-httpclient in you classpath), and then <a href="http://jakarta.apache.org/commons/httpclient/logging.html">turn on the debug logging</a>.</p>
+<p>You will then have very detailed information on how your url is handled. If you still have problem, ask for help on the <a href="forum/core.html">forum</a>.</p>
+<h2>What if I do not want to put my library files in the lib directory ? </h2>
+<p>No problem, you just have to set an ant property:</p>
+<code><property name="ivy.lib.dir" value="pathtomylibdir"/></code>
+<h2>What if I do not want the revision of the files I retrieve to appear in the<br />
+file name ?</h2>
+<p>A typical question for people using an IDE like eclipse and often changing<br />
+dependency revision: it's a bit boring to change your IDE project just to tell<br />
+him to use comp-build2596.jar instead of comp-build2595.jar, when you have<br />
+already changed your ivy file (and even if you haven't changed it, if you use<br />
+the continuous integration feature !). No problem, you have a total control on<br />
+the files retrieved using the pattern attribute in the retrieve task:</p>
+<p>Here is the default pattern:</p>
+<code><ivy:retrieve pattern="${ivy.lib.dir}/[artifact]-[revision].[ext]"/></code>
+<p>And here is one which do not suffix file name with dependency revision:</p>
+<code><ivy:retrieve pattern="${ivy.lib.dir}/[artifact].[ext]"/></code>
+<p>And one which makes your lib directory have the same layout as the ibiblio repository:</p>
+<code><ivy:retrieve pattern="${ivy.lib.dir}/[module]/[type]s/[artifact]-[revision].[ext]"/></code>
+<p>Not too difficult, and really flexible, isn't it ? And check the retrieve task<br />
+reference documentation to learn more about it...</p>
+<h2>Why two xml files ?</h2>
+<p>Ivy uses two types of xml files: configuration files and ivy files.</p>
+<p>In fact, Ivy distinguishes two different steps to describe and get your<br />
+dependencies:<br />
+You write ivy files to describe the dependencies of your module, independently of how you retrieve them.<br />
+Then you configure ivy to indicate where it can find your dependencies. Thus you can easily share your ivy files, even if you have internal dependencies which are not resolved the same way in your environment as in the target development environment. You just need to write two configuration files, one in your default development environment, and one in the target development environment with the <b>same ivy files</b>. </p>
+<h2>How do I separate the dependencies I need at xxx time and the one I need at yyy time ?</h2>
+<p>Ivy uses a concept called <i>configurations</i> to handle this, and many more. As explained in the <a href="doc/terminology.html">terminology page</a>, a <i>configuration</i> of your module can be thought as a way to use your module (<i>note: this has nothing to do with the configuration of ivy itself, through the use of configuration file</i>). You can describe what dependencies are needed in each configuration. </p>
+<p>Moreover, because the dependencies are modules too, they can also have configurations. What is extremely powerful with ivy is that you can define configurations mapping, i.e. which conf of the dependency is needed in which conf of your module. Thus what is needed at 'runtime' of a dependency can be needed for 'test' of your module.</p>
+<p>Finally, the configurations are unlimited, defined in each module, and can extend each other. This contributes a lot to ivy flexibility.</p>
+<h2>How do I configure Ivy to find ivy files in both a local repository and ivyrep ?</h2>
+<p>A frequent configuration of Ivy is to use a local repository + ivyrep + ibiblio to store ivy files and artifacts.<br />
+Here is a sample configuration to do this:</p>
+<code>
+<ivyconf>
+  <properties file="${ivy.conf.dir}/ivyconf.properties"/>
+  <conf defaultCache="cache" defaultResolver="libraries"/>
+  <resolvers>
+    <dual name="libraries" >
+      <chain name="ivy-chain" returnFirst="true">
+        <filesystem name="local-ivy"> 
+          <ivy pattern="${locallibrep}/[organisation]/[module]/[revision]/ivy.xml" /> 
+        </filesystem>
+        <ivyrep name="ivyrep"/>
+      </chain>
+      <chain name="artifact-chain" returnFirst="true">
+        <filesystem name="local-artifact"> 
+          <artifact pattern="${locallibrep}/[organisation]/[module]/[revision]/[type]s/[artifact].[ext]" /> 
+        </filesystem>
+        <ibiblio name="ibiblio"/>
+      </chain>
+    </dual>
+  </resolvers> 
+</ivyconf>
+</code>
+<h2>Can I write an ivy file for a module with no artifact at all ?</h2>
+<p>Yes, this is what is called a 'virtual' module.</p>
+<p>Having a module which has no publication and only dependencies can be useful in many cases. </p>
+<p>In particular, you can in this way define a set of dependencies used in several projects. Once defined, you can simply add a dependency on this virtual module to get all its dependencies, thanks to transitive dependencies management.</p>
+<p>It can also be useful if you want to define a flexible framework. In your framework, you will certainly have several modules, each having its own dependencies. But for the users of your framework, it can be interesting to provide a virtual module, representing the framework as a whole, and using configurations to let the user choose what he really wants to use in your framework, in a very flexible and effective way.</p>
+<p>But the problem is that ivy considers by default that a module publishes one artifact, with the same name as the module itself. So the way to define a virtual module is to add to its ivy file a publications section with no publication inside:</p>
+<code><publications/></code>
+<h2>I do not manage to get xxx module on ibiblio. What's wrong ?</h2>
+<p>The problem can come from several places... usually it comes from the fact that some modules on ibiblio do not respect a clean structure.</p>
+<p>For instance, opensymphony projects are all in an opensymphony directory, which does not respect the [module]/[artifact]-[revision].[ext] pattern. In this case the only way to go with this is to configure another resolver with the appropriate pattern, and configure ivy to use this resolver for opensymphony only.</p>
+<p>Another similar problem is to have several modules in one directory, such xerces and xmlapis in the xerces directory. The problem is that if you consider the two as one module, you will be tempted to declare a dependency on two revisions of this module. This is not the right approach, because this does not match ivy definition of a module. A better approach is similar to the preceding one with a special configuration for this only.</p>
+<p>Another solution is to setup a local repository for those modules that are not cleanly deployed on ibiblio. Using this local repository first and the ibiblio repository after is a good way to turn around the problems of ibiblio and still benefit from the huge number of artifacts that can be found.</p>
+<h2>When I update an ivy file in my repository ivy do not take the change into account. Is this normal ?</h2>
+<p>This the default behaviour of ivy, which relies on the revision and on its cache to avoid too many downloads. However, this can be changed on each resolver using the <em>checkmodified</em> attribute, or globally by setting <em>ivy.resolver.default.check.modified</em> variable to true.</p>
+<h1>Misc</h1>
+<h2>Where are the release notes ?</h2>
+<p>Release notes can be found in the <a href="doc/releasenotes.html">documentation</a>.</p>
+<h2>Where can I get more information?</h2>
+<p>If you need more information about Ivy than the one found in the documentation, you can see the <a href="links.html">links</a> page, use the <a href="forum/core.html">forum</a> to ask your question to the community, or use your favorite search engine.<br />
+For search engine search, we advise to use ivy + ant or java as base keywords, since ivy alone is a very common word.</p></textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/features.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/features.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/features.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/features.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,64 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<p>Ivy is a very powerful dependencies manager oriented toward java dependency management, even if it can be used to manage dependencies of any kind.</p>
+<p>If you don't see why you should use a dependency manager at all, or have any question concerning Ivy in general, have a look at the <a href="faq.html">FAQ</a> and at the [[mailing-lists]].</p>
+<h1>Integrated with ant</h1>
+<p>Of course, Ivy is integrated with the most popular build management system for java projects. But the integration goes way beyond common ant integration. Indeed Ivy has been designed with ant integration and design principles in mind. If you have ant skills, you will have ivy skills! The plugin mechanism in ivy follow the same design as ant one, you will find macrodef and files import in ivy configuration, many things with which ant users are already familiar.<br/>
+And since Ivy is now an Apache project, we are getting even closer to Ant development.</p>
+<h1>Simple to use</h1>
+<p>For simple cases, ivy is really simple to use. Declare your dependencies, and that's all. See the <a href="doc/tutorial/start.html">quick start tutorial</a> to check yourself, it should take less than 5 minutes!</p>
+<p>Ivy can thus be used to bring the dependency management feature of maven to ant build files, for those of you who already use ant and who do not want to setup a maven project. But Ivy does not stop here, and provides much more great features!</p>
+<h1>Clean dependency reports</h1>
+<p>Ivy is able to produce mainly two kind of reports: html reports and graph reports. HTML reports gives you a good understanding of what ivy did, and which dependencies your project depends upon. The graph reports let you have a good overview of the transitive dependencies (see below) and conflicts in your project.</p>
+<p>Here are some samples of what ivy generates for you:<br />
+<center><br />
+<a href="samples/ivy-sample-xslt.xml"><img src="images/ivyfile-small.png" title="browsable ivy file through simple xslt"/></a> <a href="images/hibgraph.png" alt="ivyfile"><img src="images/hibgraph-small.png" title="full dependency graph"/></a> <a href="samples/jayasoft-ivyrep-example-default.html" alt="graph"><img src="images/report-small.png" title="detailed dependency report" alt="report"/></a><br />
+</center></p>
+<h1>Non intrusive</h1>
+<p>Ivy most common use is to resolve dependencies and copy them in the lib dir of your project. Once copied, your build does not depend on ivy any more. Thus you can easily migrate existing builds using the lib dir pattern to store dependencies. Moreover, you can easily deliver your project with its dependencies so that the build file does not depend on ivy.</p>
+<h1>Extremely flexible</h1>
+<p>With Ivy, you usually do not have to adapt your project to ivy structure, it's ivy which can be adapted to your environment.</p>
+<p>Even if Ivy comes with a lots of default values to work out of the box, you can change many things in ivy. Of course, the dependencies repositories possibilities covers a lot of uses (file system, url based, repository chaining, ...). But that's not all. You can change the way ivy finds latest versions of your dependencies, you can change of conflict manager, you can choose if you want ivy to copy deps in your project libs or to use them directly from ivy cache, ...</p>
+<h1>Easily extensible</h1>
+<p>When ivy does not what you want out of the box, you can often extend it to solve your problem. For instance, you can plug your own repository (like scott haug did for a svn repository now available in ivy tools). But you can also defines your own latest strategy and your own conflict manager. See <a href="doc/extend.html">how to extend ivy</a> in the reference doc. </p>
+<p>Since Ivy 1.4 you can even define very easily your own metadata on your modules, with <a href="doc/concept.html#extra">extra attributes</a>.</p>
+<h1>High performances</h1>
+<p>In Ivy, performances have been taken in consideration from the beginning. It uses a cache to avoid downloading twice a dependency, its strong conflict management system has been thought to avoid downloading a dependency if not necessary, all configuration and ivy file parsing are done using SAX for maximum performance, and so on...</p>
+<h1>Transitive dependencies</h1>
+<p>Imagine you have a component that you often reuse in your software developments. Imagine that this component has itself dependencies. Then with classical dependencies management, each time you use this component in your software you have to declare it as a dependency, but also all its dependencies.</p>
+<p>With ivy it's different: you simply write a dependency file once for the component, declaring its own dependencies, then anytime you want to use this component you simply have to declare a dependency on it.</p>
+<p>And this is even more powerful if the component your software depends on changes of dependencies during its own development. Then, without ivy, you have to maintain all your components dependencies declaration each time the dependencies of this component change. With ivy, you update the ivy file of the component and that's it !</p>
+<p><i>If you want to quickly start using this feature or simply see it in action with real world examples, check the official repository: <a href="ivyrep.html">ivyrep</a></i></p>
+<h1>Strong conflict management</h1>
+<p>The problem with transitive dependencies is that it's sometimes difficult to know exactly which version of a dependency you get, because several modules are depending on it in different versions. Ivy provides a strong and flexible conflict management engine, which let you easily choose which version should be evicted or kept if its default behaviour does not fit your needs. </p>
+<p>It is also fully integrated with transitive dependencies management, which means that conflicts are solved for each dependency before being solved for your whole module. This  ensures that problematics conflicts will only need to solved in the dependency they are encountered.</p>
+<h1>Out of the box ibiblio repository support</h1>
+<p>Maven users all know this repository, where you can find a lot of java projects artifacts. With ivy, you benefit from this repository out of the box. But you even benefit from more, since Ivy also uses its <a href="http://ivyrep.jayasoft.org/">own repository</a> for dependencies metadata, leveraging the power of transitive dependencies.</p>
+<h1>Continuous Integration Ready</h1>
+<p>Are you working in a continuous integration environment ? No ? You should ;-)</p>
+<p>If you are working in a continuous integration environment, and if you have many projects that depend one on each other, then you are maybe experiencing the dependency management nightmare... Fortunately, ivy is there to help !</p>
+<p>With ivy you can declare that a component depends on the latest version of another component. Knowing that, ivy will search for the latest version of the dependency whenever you ask it to do so. This latest version is computed by ivy simply either by checking the date of the dependency versions or by comparing versions as text (either lexicographically or with an algorithm close to the one used in php version_compare function).</p>
+<h1>Publication handling</h1>
+<p>Ivy handles for you the publication of your projects to your repository, as defined in ivy. This simplifies a lot the management of multi-project environment.</p>
+<h1>Pluggable module descriptor parsers</h1>
+<p>Ivy is able to use ivy files as module descriptors, but also maven2 poms, or even your own module descriptors! This can help you move softly from an existing repository of modules to an ivy managed one.</p>
+<h1>Unique enterprise features</h1>
+<p>Ivy is the only dependency management tool to support powerful features such as repository namespace and building through the install task. A <a href="doc/tutorial/build-repository.html">tutorial</a> is dedicated to this feature, and show you how you can build your own repository importing data from public one, and converting heterogeneous repositories into a stable and homogeneous one.</p>
+<h1>Heavily tested</h1>
+<p>Ivy benefits from a lot of unit tests checked at each change. It is also under heavy tests by the community itself, and bugs reported by the community are often fixed in only a few days.</p>
+<h1>Supported by several tools</h1>
+<p>A growing number of tools support ivy, see the <a href="links.html">links</a> page for details.</p>
+<h1>Free and open source</h1>
+<p>Ivy is an incubating Apache project, which means that it's fully open sourced, with a business friendly Apache license.</p>
+<p>Being open source, you can even modify it for your own needs, and make the community benefit from your enhancements if you like.</p>
+<h1>Extensively documented</h1>
+<p>With Ivy, not only the tool is free and open source, but you also have access to a documentation of about 120 pages in its printer friendly version for free!</p></textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/get-involved.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/get-involved.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/get-involved.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/get-involved.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+As an Apache Incubator project, Ivy is very open to external contributions.
+
+There are many ways to contribute to Ivy.
+
+First, [[download]] and use it, subscribe to the [[mailing-lists]], and answer to other user questions. You can also browse [[issues jira issues]], vote for the one you are most interested in, add your comments and feedback.
+
+When you browse the documentation, whenever you see something that could be improved, feel free to edit it and provide a documentation patch. It's very easy if you browse the documentation offline (in src/doc if you check out Ivy from svn), you will see a small toolbar at the upper left of the page, which allows you to edit the page. Then all you have to do is attach your modification as a patch to a new issue in JIRA.
+
+You can also provide brand new documentation pages, tutorials, demo, or even links to a tutorial on your own blog. Another useful way to contribute is to spread the word: if you like Ivy, say it! On your blog, on other blog comments, on popular java related sites, wherever. The more Ivy is popular, the more it will get external contributions, and the better it will be, for the benefit of the whole community.
+
+When you get more confident with Ivy, you can check it out from svn, and begin to see if there are issues you could fix or implement, and provide patches to make the whole community benefit from your work.
+
+When you provide a patch, to increase the chance to get integrated, do not forget to provide a junit test, and a patch to the documentation if it changes anything in Ivy behaviour.
+
+And if you often provide patches and answers on the mailing lists, you may get the chance to become a commiter, with write access to the svn repository!</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/images/hibgraph-small.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/hibgraph-small.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/hibgraph-small.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/hibgraph.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/hibgraph.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/hibgraph.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/ivy-book.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/ivy-book.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/ivy-book.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/ivy-demo.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/ivy-demo.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/ivy-demo.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/ivy-dl-1.4.1.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/ivy-dl-1.4.1.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/ivy-dl-1.4.1.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/ivy-forum.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/ivy-forum.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/ivy-forum.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/ivy-lierre.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/ivy-lierre.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/ivy-lierre.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/ivyfile-small.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/ivyfile-small.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/ivyfile-small.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/main-tasks.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/main-tasks.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/main-tasks.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/report-small.png
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/report-small.png?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/report-small.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step1.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step1.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step1.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step2.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step2.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step2.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step3-2.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step3-2.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step3-2.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step3.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step3.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step3.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step4.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step4.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step4.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step5.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step5.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step5.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step6.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step6.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step6.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/images/yed-step7.jpg
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/images/yed-step7.jpg?view=auto&rev=491923
==============================================================================
Binary file - no diff available.

Propchange: incubator/ivy/trunk/src/doc/xooki/images/yed-step7.jpg
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/ivy/trunk/src/doc/xooki/index.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/index.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/index.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/index.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,21 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<table border="0" class="home">
+<tr><td colspan="4"><img src="images/ivy-lierre.png"/></td></tr>
+<tr style="font-size:xx-large;"><td colspan="4"><span style="font-size:xx-large;">The agile dependency manager</span></td></tr>
+<tr><td colspan="4" style="font-size:large; padding: 1cm 0 0.7cm 0;">Ivy is a popular dependency manager focusing on flexibility and simplicity.<br/>
+Find out more about its unique <a href="features.html">enterprise features</a>, what <a href="testimonials.html">people say about it</a>,<br/>
+and <a href="doc.html">how it can improve your build system!</a></td></tr>
+<tr class="homeitems"><td><a href="download.html"><img src="images/ivy-dl-1.4.1.png"/></a></td><td><a href="doc.html"><img src="images/ivy-book.png"/></a></td><td><a href="demo.html"><img src="images/ivy-demo.png"/></a></td><td><a href="mailing-lists.html"><img src="images/ivy-forum.png"/></a></td></tr>
+<tr class="homeitems"><td><a href="download.html">download</a></td><td><a href="doc.html">documentation<br/>& tutorials</a></td><td><a href="demo.html">demo</a></td><td><a href="mailing-lists.html">share your experience</a></td></tr>
+</table>
+</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/issues.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/issues.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/issues.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/issues.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,15 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Issues are tracked using JIRA hosted at Apache:
+http://issues.apache.org/jira/browse/IVY
+
+Feel free to browse what are the bugs already reported for each version, what are the features planned for next versions, and contribute your own feedback by submitting bug reports or feature requests, patches, comments, or simply by voting for your favorite issues.</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Modified: incubator/ivy/trunk/src/doc/xooki/ivyrep.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/ivyrep.html?view=diff&rev=491923&r1=491922&r2=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/ivyrep.html (original)
+++ incubator/ivy/trunk/src/doc/xooki/ivyrep.html Tue Jan  2 12:14:12 2007
@@ -5,11 +5,11 @@
 	<script type="text/javascript" src="xooki/xooki.js"></script>
 </head>
 <body>
-	<textarea id="xooki-source">
-IvyRep is the official  ivy repository. For the moment, it only stores ivy files, artifacts being most of the time found on ibiblio.
-
-You can find more information on ivyrep on its own home page:
-<a href="http://ivyrep.jayasoft.org/">http://ivyrep.jayasoft.org/</a>.
+	<textarea id="xooki-source">
+IvyRep is the official  ivy repository. For the moment, it only stores ivy files, artifacts being most of the time found on ibiblio.
+
+You can find more information on ivyrep on its own home page:
+http://ivyrep.jayasoft.org/.
 	</textarea>
 <script type="text/javascript">xooki.postProcess();</script>
 </body>

Added: incubator/ivy/trunk/src/doc/xooki/license.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/license.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/license.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/license.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,43 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Now that Ivy is an Apache Incubator project, it is available under an Apache v2.0 license.
+
+The releases prior to and including 1.4.1 were released under a BSD license:
+<code>
+BSD License for Ivy
+Copyright (c) 2005, JAYASOFT
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification, 
+are permitted provided that the following conditions are met:
+
+    * Redistributions of source code must retain the above copyright notice, 
+      this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above copyright notice, 
+      this list of conditions and the following disclaimer in the documentation 
+      and/or other materials provided with the distribution.
+    * Neither the name of JAYASOFT nor the names of its contributors 
+      may be used to endorse or promote products derived from this software 
+      without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND 
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 
+
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR 
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON 
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS 
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+</code></textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/links.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/links.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/links.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/links.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+<h1>Repositories</h1>
+<ul>
+<li><a href="http://ivyrep.jayasoft.org/">IvyRep</a></li>
+<p> The main repository of ivy files used by Ivy.</p>
+<li><a href="https://opensvn.csie.org/ivyrepsandbox/">IvyRep Sandbox</a></li>
+<p> This subversion repository is used to share ivy files before promoting them to ivyrep.</p>
+<li><a href="http://www.ibiblio.org/maven/">IBiblio maven repository</a></li>
+<p> The official repository of maven hosts a great number of jars. It can be used by ivy to find the jars of your depedencies.</p>
+<li><a href="http://www.opensymphony.com/webwork/wikidocs/Dependencies.html">Webwork ivy repository</a></li>
+<p> Open symphony has created an ivy repository you can use as a model or directly.</p>
+<li><a href="http://blog.tryphon.org/tryphon/archives/2006/09/02/kolaka-ivy-repository/">Kokala repository</a></li>
+<p> Folks from FreeCast have created an ivy repository for building FreeCast. You will find many interesting ivy files over here.</p>
+<li><a href="https://maven-repository.dev.java.net/">Java.net Maven repository</a></li>
+<p>Java.net has a maven repository with interesting stuff that can't be found on ibiblio</p>
+<li><a href="http://mvnrepository.com/">mvnrepository</a></li>
+<p> Search Maven Ibiblio repository
+</ul>
+<h1>Tools and plugins</h1>
+<p>Here is a list of the ivy related tools and plugins we are aware of that can be found over the net.</p>
+<p>Feel free to post on the forum to ask for your tool to be added here.</p>
+<ul>
+<li><a href="http://www.ivytools.org/">ivytools.org</a></li>
+<p> This sourceforge project aims to gather community contributed tools and plugins for ivy.</p>
+<li><a href="../ivyde.html">IvyDE</a></li>
+<p> A plugin for eclipse which helps writing ivy files by bringing powerful code completion and wizards, and also let you add a classpath container keeping your eclipse project classpath in sync with the dependencies ivy resolves.</p>
+<li><a href="http://ivycruise.jayasoft.org/">IvyCruise</a></li>
+<p> This set of plugins for cruise control let you integrate ivy with this famous continuous integration server.</p>
+<li><a href="http://plugins.intellij.net/plugin/?id=141">IvyDependencyImportor</a></li>
+<p> is a plugin for intellij IDEA, which let you import all the libs described in the ivy.xml to the current module library.</p>
+<li><a href="http://plugins.intellij.net/plugin/?id=140">IVY for IDEA</a></li>
+<p> is another plugin for intellij IDEA, which reads IDEA module settings such as classpath and source directories from IVY setup.</p>
+<li><a href="http://www.ivytools.org/ivy+svn.html">Ivy+SVN</a></li>
+<p> This is a subversion dependency resolver for ivy.</p>
+<li><a href="http://wiki.hippo.nl/display/OS/SAnt+build+system">SAnt</a></li>
+<p> SAnt (Shared Ant) is an experimental build system based on Ant and Ivy, primarily developpedd as part of the hippo project.</p>
+<li><a href="http://dehora.net/code/antant/readme.html">AntAnt</a></li>
+<p> AntAnt is an ant project generator (generates an ant project skeleton), which uses ivy for dependency management.</p>
+<li><a href="http://www.fnogol.de/archives/2006/08/21/generate-applicationxml-from-ivyxml-for-packaging-an-ear/">Generate application.xml from ivy.xml for packaging an ear</a></li>
+<p> is an entry on Philipp Meier's weblog which explain how he used ivy and xslt to generate his application.xml files.</p>
+<li><a href="http://www.ribomation.com/riboutils/eartask/">EAR ant task</a></li>
+<p> this is not directly related to ivy, but more to the link above. You have also the possibility to use this task to generate your ear, which does not depend on Ivy, but which can be very easily integrated with.</p>
+</ul>
+<h1>External Doc and tutorials</h1>
+<ul>
+<li><a href="http://wiki.java.net/bin/view/Netbeans/FaqIvy">Netbeans FAQ</a></li>
+<p>The Netbeans FAQ has an entry explaining how to use Ivy in their open source IDE.</p>
+<li><a href="http://chris-engn.blogspot.com/2005/07/naven-dotnet-continous-integration.html">Using Ivy in a dotnet project</a></li>
+<p>Chris gives a good idea of how to use ivy, cruise control and nant in a dotnet project environment</p>
+<li><a href="http://weblogs.java.net/blog/dcengija/archive/2006/04/configuring_ivy.html">Integrating Ivy and luntbuild</a></li>
+<p>Davor Cengija on his blog explain how he integrates Ivy in luntbuild, an open source continuous integration server</p>
+<li><a href="doc/articles/ease-multi-module.html">Easing multi module development</a></li>
+<p>Johan stuyts, the author of SAnt, also contributed a nice article on his view of how to use Ivy on a multi module environment.</p>
+<li><a href="http://www-128.ibm.com/developerworks/java/library/j-ap10106/index.html?ca=dgr-jw01SmellyScripts">Remove the smell from your build scripts</a></li>
+<p>This article is not related to Ivy, but to build script in general, but we thought it may be worth for Ivy users to read it.
+</ul>
+<h1>Others</h1>
+<ul>
+<li><a href="http://ant.apache.org/">ant</a></li>
+<p>Ant is the popular build tool with which ivy is integrated.</p>
+<li><a href="http://ant-contrib.sourceforge.net/">AntContrib</a></li>
+<p>AntContrib is a project offering a set of useful tasks for ant.</p>
+<li><a href="http://www.javalobby.org/">Javalobby</a></li>
+<p>Javalobby is a Java community site with interesting forums and tutorials</p>
+</ul></textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>

Added: incubator/ivy/trunk/src/doc/xooki/mailing-lists.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/mailing-lists.html?view=auto&rev=491923
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/mailing-lists.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/mailing-lists.html Tue Jan  2 12:14:12 2007
@@ -0,0 +1,26 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html>
+<head>
+	<script type="text/javascript">var xookiConfig = {level: 0};</script>	
+	<script type="text/javascript" src="xooki/xooki.js"></script>
+</head>
+<body>
+	<textarea id="xooki-source">
+Ivy uses the standard Apache way to communicate: mailing lists.
+
+Before posting, make sure you don't have the answer to your question in the [[faq]] or more generally in the [[doc]].
+
+The available mailing lists are:
+<table>
+<tr><td>ivy-user@incubator.apache.org</td><td>Used to discuss any issue encountered when using Ivy</td></tr>
+<tr><td>ivy-dev@incubator.apache.org<td>Used to discuss Ivy development</td></tr>
+<tr><td>ivy-commits@incubator.apache.org<td>Read only mailing list where subversion commit messages are posted</td></tr>
+</table>
+<br/><br/>
+The previous way of communication around Ivy was the Jayasoft forum, for which a backup is still available here:
+http://www.jaya.free.fr/ivy/forum.html
+
+Feel free to use your favorite search engine to find answers to your questions in over there.</textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>



Mime
View raw message