You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by xa...@apache.org on 2006/12/18 17:06:13 UTC
svn commit: r488342 [4/9] - in /incubator/ivy/trunk/src/doc/xooki: ./ doc/
doc/conf/ doc/configuration/ doc/configuration/macrodef/
doc/configuration/namespace/ doc/ivyfile/ doc/releasenotes/ doc/resolver/
doc/tutorial/ doc/tutorial/build-repository/ d...
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc1.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc1.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc1.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,27 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+- add report task, which enables to generates reports of dependencies, including a graph ready to be layed out by yEd
+- add exclude feature in dependency
+- include exclude feature now handles regexps
+- new latest strategy: latest revision now uses a "php version_compare" like algorithm, whereas lexicographic comparison is now available in latest lexicographic
+- enhance xml resolve report details
+- FIX: better separation between root configurations
+- FIX: XmlModuleDescriptorUpdater now preserves xml header
+- FIX: modules figures in report (displayed at the end of resolve)
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc1-bin.zip">ivy-1.0-rc1-bin.zip</a> (1161 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc1-src.zip">ivy-1.0-rc1-src.zip</a> (984 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc1-src-withdep.zip">ivy-1.0-rc1-src-withdep.zip</a> (1247 kB)
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc2.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc2.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc2.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc2.html Mon Dec 18 09:06:07 2006
@@ -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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+- IMPROVE: improved messages: more debug, more verbose, and more details on failures
+- FIX: bug with '\' in path patterns
+- FIX: bug with relative paths patterns
+- FIX: configure task tries ivy.conf.file as relative to base dir and to current dir
+- FIX: file system resolver publishes ivy files with ivy pattern
+- FIX: 0 content length considered as non existing (behaviour of jre 5.0 on linux)
+ => empty ressources are now considered as non existing
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc2-bin.zip">ivy-1.0-rc2-bin.zip</a> (1164 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc2-src.zip">ivy-1.0-rc2-src.zip</a> (987 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc2-src-withdep.zip">ivy-1.0-rc2-src-withdep.zip</a> (1250 kB)
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc3.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc3.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc3.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0-rc3.html Mon Dec 18 09:06:07 2006
@@ -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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+<i>A few bugs have been discovered in the 1.0-rc2, so here is the reason for this rc3, which should fix these bugs.
+If no bug is discovered, 1.0-rc3 should be promoted to 1.0 on <b>2005-04-26</b></i>
+- IMPROVE: added debug messages on variables setting
+- FIX: ivyconf now able to load a properties file given as url
+- FIX: deliver pub date now actually defaults to 'now'
+- FIX: all tasks attributes now substitute ivy variables
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc3-bin.zip">ivy-1.0-rc3-bin.zip</a> (1168 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc3-src.zip">ivy-1.0-rc3-src.zip</a> (993 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-rc3-src-withdep.zip">ivy-1.0-rc3-src-withdep.zip</a> (1256 kB)
+
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.0.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,27 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+1.0-rc3 has been promoted to 1.0 on 2005-04-26
+
+See child pages for details about changes introduced by each release candidate
+
+<i>Known bugs and limitations:</i>
+- cyclic dependencies result in StackOverflowError
+- infinite loop in rare cases when a conflict occur between a latest subversion and a fully resolved revision
+- url connections not closed properly when not using commons-httpclient
+- latest does not work with http urls in some cases, when the name of the link is truncated in the web page
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-bin.zip">ivy-1.0-bin.zip</a> (1166 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-src.zip">ivy-1.0-src.zip</a> (904 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.0-src-withdep.zip">ivy-1.0-src-withdep.zip</a> (1167 kB)
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.1.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.1.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.1.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,50 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+- remote configuration (if available) of ivyrep and ibiblio patterns and roots
+- new detailed messages when ivy fails to reach an url (thanks to Nicolas)
+- new artifactproperty task, which enables to set a property for each dependency artifacts resolved by ivy
+- new defaultconf attribute in ivy file dependencies, to change the default conf to use in the file when no conf is specified for a dependency
+- add the ability to change the xsl file and report name pattern used by report task
+- http listing now compatible with tomcat listing (tested with 5.0.28)
+- pub revision in deliver task now defaults to timestamp if not provided by any other way
+- debug messages improvements, with configuration dump among others
+- new var task, enables to set ivy variables from ant
+- now defaults for ivyrep and ibiblio resolver are configurable by variables
+- refactoring: introduce the notion of BasicResolver, Repository, Resource, RepositoryResolver, making much easier the task of writing basic resolvers
+- added checkmodified attribute on all basic resolvers, which defaults to ${ivy.resolver.default.check.modified}
+ This makes ivy check last modified date of ivy files to see it its cache is up to date
+- artifacts download are now first made to a temp file, which is renamed only at the end of the download.
+ This prevent interrupted downloads to be considered as finished
+- FIX: handle proxy configuration with http-client (thanks to Nicolas)
+- FIX: remove dependency on ant outside of ant integration classes
+- FIX: resolve problem when conflicts on latest revisions
+- FIX: allow use of any kind of URL in IvyRepResolver (both ivyroot and artroot) and IBibiblioResolver
+- FIX: chain resolver can now be used for artifacts part of dual resolver
+- FIX: now detects and warn about circular dependencies
+- FIX: cachepath task now takes pathid as parameter instead of id, to prevent
+ special handling from ant
+- FIX: ivy.xsd: set artifact minOccurs to 0 in publications
+
+Thanks to John Shields from Robert Half International, Inc.:
+- FIX: no more infinite loop when a conflict occurs between a latest subversion and a fully resolved revision
+- FIX: BasicURLHandler now closes its connections
+- FIX: ApacheURLLister now works with capital letter in revisions and truncated names
+- now use of ivy variables is allowed in ivy files
+- added a null check in pattern helper substitute
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.1-bin.zip">ivy-1.1-bin.zip</a> (999 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.1-src.zip">ivy-1.1-src.zip</a> (738 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.1-src-withdep.zip">ivy-1.1-src-withdep.zip</a> (1001 kB)
+
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.2a.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.2a.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.2a.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.2a.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,49 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+<i>Note: due to a bad delivery operation, version 1.2 found on this site from 2005-09-14 to 2005-09-16 was not the intended 1.2 version. Please use 1.2a instead</i>
+
+- new ivy.deps.changed property set if there are changes since last resolve (IVY-71)
+- new buildlist task: calculate order of dependencies of subprojects for easy multi-projects builds (IVY-69)
+- accept organization as token (IVY-55)
+- added type filtering mechanism on resolve task (IVY-45)
+- detect and warn about resolver using ivy cache as repository (IVY-53)
+- new transitive attribute on dependency, which enable to disable transitive dependency management on a particular dependency (thanks to Ingo Adler) (IVY-20)
+- new '@' in dependency configuration mapping declaration, used to indicate that a configuration maps to itself useful with *, '*->@' meaning that all configurations of the module maps to their equivalent (same name) in the dependency (IVY-52)
+- new changing attribute on dependencies indicate that the dependency artifacts may change even without revision change, but with only a new ivy file with new publication date
+- new useRemoteConfig on conf tag in ivyconf.xml, tells to use remote configuration file for repository config
+- new type filtering in cachepath task
+- new cachefileset task: builds an ant fileset of artifacts in cache
+- publish task now uses srcivypattern for ivy files finding and for delivery
+- better debug and error messages (IVY-60 IVY-61)
+- added a javadoc target in ant build (thanks to joshua nichols)
+
+- FIX: module descriptors sort was failing in some case cases (fix by Karl Baum)
+- FIX: Ivy complains about schema directive (IVY-64)
+- FIX: 'null' status attribute in module descriptor (IVY-62)
+- FIX: report header contains incorrect link after resolve for multiple, comma-separated configurations (IVY-57)
+- FIX: error retrieving dependencies with a '+' in their revision if the ivy file doesn't exist - fixed by maarten coene (IVY-59)
+- FIX: trying to resolve latest with no revision in pattern caused a StackOverflowError (IVY-56)
+- FIX: now handle transitive eviction (IVY-51)
+- FIX: resolve now store resolved file id in ivy variables, so that multiple resolve calls can be followed by multiple retrieve, each retrieve will use the last resolve info (IVY-49)
+- FIX: IllegalStateException on retrieve done from command line
+- FIX: checks ivy files data consistency with asked info (org, module name and revision)
+- FIX: use AUTH configuration for configuration file
+- IMPROVE: added publish handling from command line (IVY-48)
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.2a-bin.zip">ivy-1.2a-bin.zip</a> (1028 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.2a-src.zip">ivy-1.2a-src.zip</a> (776 kB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.2a-src-withdep.zip">ivy-1.2a-src-withdep.zip</a> (1040 kB)
+
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc1.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc1.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc1.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,79 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+<em>compatiblity with previous version:
+- the default place for the cache has changed, it is now in {USER_HOME}/.ivy/cache, instead of {USER_HOME}/.ivy-cache
+ please move this directory if you want to avoid unnecessary downloads
+- modules are now logged as they are found, set ivy.log.module.when.found variable to false to avoid this</em>
+
+- NEW: namespace system: a resolver can be declared to belong to a namespace, which itself specify the transformation to apply to convert it from and to system namespace (IVY-147)
+- NEW: pluggable module descriptor parsers let define new kind of module descriptor (IVY-146) (thanks to Maarten Coene)
+- NEW: a new install task let add modules found in a repository in another one, even transitively (IVY-141)
+- NEW: maven2 pom compatibility: most resolvers are now able to handle m2 pom as project metadata and there is a new convertpom task able to convert a pom file to an ivy file (IVY-140)
+- NEW: include configurations from external file (IVY-88)
+- NEW: a new default resolver which let override ivy files and artifacts found on public repository (ivyrep / ibiblio) and let publish modules in a local repository (IVY-132)
+- NEW: ivyconf file inclusion in ivyconf files (IVY-99)
+- NEW: macrodef feature in ivyconf for defining macro resolvers with parameters (IVY-98)
+- NEW: conf fallback mechanism (IVY-145)
+- NEW: exclusion now let exclude whole modules (IVY-144)
+- NEW: ability to use a dependency instead of an ivy file in standalone mode (IVY-96)
+- NEW: ability to output a path of dependencies in cache from the standalone mode (IVY-92)
+- NEW: it is now possible to reference existing resolver in resolver containers (IVY-35)
+- NEW: overwrite attribute in the publish task now let force overwrite of read only files (IVY-83)
+- NEW: add a conflict manager ("strict") making build fail when a diamond conflict is found (thanks to Christer Jonsson) (IVY-118)
+
+- IMPROVE: generate xml report using ivy:report task (IVY-143)
+- IMPROVE: possibility to configure ivy so that special revisions are not queried as fixed one at all (IVY-139)
+- IMPROVE: better url querying management (IVY-138) (thanks to Bernard Niset)
+- IMPROVE: do not add resolver info in ivy files in cache so that they can be safely used as usual ivy files in a repository (IVY-137)
+- IMPROVE: review default conf mapping management (IVY-134)
+- IMPROVE: add possibility for a chain to behave like a dual chain (IVY-131)
+- IMPROVE: add possibility to avoid overwrite of an ivy variable when setting them in ivyconf.xml (IVY-127)
+- IMPROVE: ability to exclude the root project from the buildlist (thanks to Constantine Vetoshev) (IVY-124)
+- IMPROVE: exclusion of artifacts now works on transitive artifacts, and exclusion can specify organisation and/or module (IVY-116)
+- IMPROVE: now dynamic revisions replacement by deliver task can be turned off (IVY-120)
+- IMPROVE: better performance with deep transitive dependencies
+- IMPROVE: allow optional parts in the patterns (IVY-102) (thanks to Maarten Coene)
+- IMPROVE: ability to define variable directly in ivyconf.xml (IVY-100)
+- IMPROVE: ability to use no revision in pattern with latest.integration dependency, artifacts being updated according to revision change in ivy file (if checkmodified is set to true) (IVY-95)
+- IMPROVE: ability to specify a root module in buildlist to filter out unnecessary build files (IVY-93) (thanks to Kristian Cibulskis)
+- IMPROVE: import system properties as ivy variables in standalone mode
+- IMPROVE: string identifying a module is now clearly different from a path
+- IMPROVE: better error message when publish fails due to readonly destination (IVY-83)
+- IMPROVE: some javadoc improvements (IVY-136 IVY-129) (thanks to Stephen Nesbitt)
+
+- FIX: problem resolving dependencies when 2 module versions have different configurations (IVY-151)
+- FIX: problem with inheritance between public and private conf (IVY-149)
+- FIX: no variable replacement during the deliver step (IVY-133)
+- FIX: conflict badly solved in some complex cases (IVY-130)
+- FIX: mapping on conf * now only takes public configurations (IVY-126)
+- FIX: bad dependency ivy files now causes failure (IVY-112)
+- FIX: stack overflow error in contradictory conflict cases (IVY-117)
+- FIX: publish now doesn't call deliver when not necessary (IVY-119)
+- FIX: cachefileset was returning all artifacts for empty configuration (IVY-108)
+- FIX: transitive and changing attribute were not copied in ivy files in cache (IVY-94)
+- FIX: chain resolver now support latest strategy configuration (IVY-90)
+- FIX: raise a clean error when a cyclic variable definition is found (IVY-75)
+- FIX: clean ant project reference at the end of the build to improve usability in ide launching multiple builds in the same vm (like netbeans) (IVY-87 - IVY-115)
+- FIX: ivy is now able to use simple ivy files in cache (doesn't need resolver info, use default one if no resolver is given) (IVY-86)
+- FIX: private conf not accessible from other modules (IVY-76)
+- FIX: root module configurations isolation bug fixed (IVY-84)
+- FIX: changed the place where ivy stores master ivy files in cache to not overlap with dependencies one (IVY-85)
+- FIX: bug in ResourceHelper didn't let override resource easily (IVY-80)
+- FIX: throws a circular dependency exception when a circular dependency is found instead of failing silently (IVY-79)
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.3-RC1-bin.zip">ivy-1.3-RC1-bin.zip</a> (1.41 MB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.3-RC1-src.zip">ivy-1.3-RC1-src.zip</a> (1.15 MB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.3-RC1-src-withdep.zip">ivy-1.3-RC1-src-withdep.zip</a> (1.48 MB)
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc2.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc2.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc2.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc2.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,32 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+- IMPROVE: ivy now supports ${pom.version} in poms (IVY-174)
+- IMPROVE: adds the possibility to disable concistency check (IVY-163)
+- IMPROVE: add possibility to choose matcher on include exclude and conflict manager rules in ivy files, and on resolver per module in ivyconf (IVY-161)
+- IMPROVE: add regexp management in the install ant task (IVY-154)
+
+- FIX: httclient is not registered for https urls (IVY-171)
+- FIX: post resolve tasks like retrieve or cachepath should be able to run from cache information (IVY-169)
+- FIX: resolve fails without appropriate message when cache is empty and a module in the repository has no revision (IVY-165)
+- FIX: resolve problem with configuration inheritance (IVY-164)
+- FIX: some files in cache detected by not used by Ivy for subsequent retrieves (IVY-159)
+- FIX: HTML report shouldn't display the dependencies of evicted modules (IVY-158) (thanks to Maarten Coene)
+- FIX: bug when an organisation or module or revision contains a space (IVY-157)
+- FIX: cos-nonambig warnings (IVY-156)
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/ivy-1.3-RC2-bin.zip">ivy-1.3-RC2-bin.zip</a> (1.53 MB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.3-RC2-src.zip">ivy-1.3-RC2-src.zip</a> (1.22 MB)
+<a href="./visit.php?url=./downloads/ivy/ivy-1.3-RC2-src-withdep.zip">ivy-1.3-RC2-src-withdep.zip</a> (1.60 MB)
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc3.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc3.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc3.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3-rc3.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,30 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+- IMPROVE: Retrieve task now also optionally do ivy file downloads (IVY-167) (with the contribution of Costin Leau)
+
+- FIX: ivy variable substitution in ivy files (IVY-186)
+- FIX: force attribute is not treated as it should in some cases (IVY-182)
+- FIX: problem reading 'invalid' POMs (IVY-153)
+- FIX: cryptic NPE due to spelling error in ivy.xml (IVY-177)
+- FIX: conflicts with dynamic revisions not resolved properly (IVY-181)
+- FIX: incorrect configuration definition gives misleading NullPointerException (IVY-175)
+- FIX: throw an error when using a non-existing conflict manager as default (IVY-179) (thanks to Maarten Coene)
+- FIX: eviction problem with different conflicts in multiple confs (IVY-173)
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/1.3-RC3/ivy-1.3-RC3-bin.zip">ivy-1.3-RC3-bin.zip</a> (1.56 MB)
+<a href="./visit.php?url=./downloads/ivy/1.3-RC3/ivy-1.3-RC3-src.zip">ivy-1.3-RC3-src.zip</a> (1.26 MB)
+<a href="./visit.php?url=./downloads/ivy/1.3-RC3/ivy-1.3-RC3-src-withdep.zip">ivy-1.3-RC3-src-withdep.zip</a> (1.64 MB)
+
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.1.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.1.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.1.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,33 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+This version is bugfix release, upgrade from 1.3 is strongly recommended.
+- FIX: retrieval of multiple artifacts in different configurations does not work as expected (IVY-188)
+- FIX: configuration http url include doesn't work with commons http client (IVY-203)
+- FIX: problem with conflict resolution in transitive dependencies (IVY-199)
+- FIX: pb with force when it comes after a conflict which has already been solved (IVY-193)
+- FIX: POM files that reference to the parent artifact download fails (IVY-195) (thanks to Tat Leung)
+- FIX: M2 compatibility does not take into account the . replacement for publishing artifacts (IVY-191) (thanks to Peter Hayes)
+- FIX: artifactproperty does not set the [conf] token in the pattern to the correct value. It is always set to 'default'. (IVY-123) (thanks to Peter Oxenham)
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/1.3.1/ivy-1.3.1-bin.zip">ivy-1.3.1-bin.zip</a> (1.57 MB)
+<a href="./visit.php?url=./downloads/ivy/1.3.1/ivy-1.3.1-src.zip">ivy-1.3.1-src.zip</a> (1.27 MB)
+<a href="./visit.php?url=./downloads/ivy/1.3.1/ivy-1.3.1-src-withdep.zip">ivy-1.3.1-src-withdep.zip</a> (1.65 MB)
+<a href="http://www.jayasoft.org/visit.php?url=./downloads/ivy/1.3.1/ivy-doc-1.3.1.zip">ivy-doc-1.3.1.zip</a> (1.6MB) (New! Easily browsable offline)
+<a href="./visit.php?url=./downloads/ivy/1.3.1/ivy-1.3.1.jar">ivy-1.3.1.jar</a>
+
+<em>Note: the zips distributed here before 2006-04-14 didn't include ivy.xml for ivy itself. This is now fixed, for those who want to get it you can find it here:
+<a href="./downloads/ivy/1.3.1/ivy-1.3.1.xml">ivy-1.3.1.xml</a>
+</em>
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.3.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,25 @@
+<!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: 2};</script>
+ <script type="text/javascript" src="../../xooki/xooki.js"></script>
+</head>
+<body>
+ <textarea id="xooki-source">
+<h1>Changes log</h1>
+Ivy 1.3-RC3 has been promoted to 1.3 on 2006-03-17.
+
+For known bugs and limitations please see http://jira.jayasoft.org/
+
+For detailed list of changes since 1.2a, please see changes of the three release candidates below.
+
+<h1>Downloads</h1>
+<a href="./visit.php?url=./downloads/ivy/1.3/ivy-1.3-bin.zip">ivy-1.3-bin.zip</a> (1.52 MB)
+<a href="./visit.php?url=./downloads/ivy/1.3/ivy-1.3-src.zip">ivy-1.3-src.zip</a> (1.21 MB)
+<a href="./visit.php?url=./downloads/ivy/1.3/ivy-1.3-src-withdep.zip">ivy-1.3-src-withdep.zip</a> (1.59 MB)
+
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC1.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC1.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC1.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,149 @@
+<!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: 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-RC1.
+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="./visit.php?url=./downloads/ivy/1.4-RC1/ivy-1.4-RC1-bin.zip">binaries</a></li>
+<li><a href="./visit.php?url=./downloads/ivy/1.4-RC1/ivy-1.4-RC1-src.zip">sources</a></li>
+<li><a href="http://www.jayasoft.org/visit.php?url=./downloads/ivy/1.4-RC1/ivy-1.4-RC1-doc.zip">documentation</a></li>
+</ul>
+
+It includes 30 new features, 33 improvements and even more bug fixes since Ivy 1.3.1.
+<code>
+ version 1.4-RC1 - 2006-09-17
+=================================
+Incompatibility with previous versions:
+---------------------------------------
+* usage:
+ - no known major incompatiblity
+ - build list task now requires a configured ivy instance (configure will automatically be called if you don't call it explicitly)
+ - publish now requires the published ivy file to have the published revision (automatic if you use deliver)
+
+* API:
+ - Numerous API changes especially in the BasicResolver class and subclasses due to the introduction of VersionMatcher,
+ this may break some custom dependency resolvers or other tools or plugins depending directly on Ivy API
+
+Changes:
+--------
+* thanks to Jayasoft:
+ - NEW: ivy report generate full graph from automated build (IVY-155)
+ - NEW: support for build number calculation (IVY-276)
+ - NEW: find modules in repository (IVY-275)
+ - NEW: explicitly specify artifact download URL (IVY-271)
+ - NEW: introduce branch management (IVY-269)
+ - NEW: resolve dependencies directly without using an ivy file (IVY-268)
+ - NEW: ability to invoke any build scripts for dependencies (IVY-68)
+ - NEW: support sftp repository (IVY-267)
+ - NEW: pluggable version matcher (IVY-219)
+ - NEW: support for version ranges (IVY-295)
+ - NEW: dependency based on dependency status (IVY-47)
+ - NEW: add possibility to define extra attributes in ivy files (IVY-217)
+ - NEW: option to omit specific confs and allow the rest (IVY-66)
+ - NEW: use custom classloader for plugins (IVY-220)
+ - NEW: adding to SPECIAL_MEANINGS in LatestRevisionStrategy (IVY-121)
+ - NEW: Allow use of system properties in ivyconf.xml (IVY-228)
+
+ - IMPROVE: allow to use file-system repository directly without cache (IVY-211)
+ - IMPROVE: deliver task use a default value for revision (IVY-252)
+ - IMPROVE: better documentation distribution (IVY-274) - in progress
+ - IMPROVE: define conflict manager per organisation/module in ivyconf (IVY-270)
+ - IMPROVE: transitive parameter in resolve (IVY-21)
+ - IMPROVE: add syncing feature in retrieve (IVY-33)
+ - IMPROVE: use of md5 and/or sha1 files to check downloads (IVY-27)
+ - IMPROVE: possible to use m2compatible without automatically using POMs as well (IVY-263)
+ - IMPROVE: support for circular dependencies (IVY-202)
+ - IMPROVE: make status list configurable (IVY-242)
+ - IMPROVE: use only ivy patterns for listing revisions when module desciptor is required (allownomd = false) (IVY-166)
+ - IMPROVE: implement strict haltonfailure if ivy.xml is not found (IVY-110)
+ - IMPROVE: artifact's "name" attribute could be omitted (IVY-231)
+ - IMPROVE: ivy standalone now return error status (IVY-152)
+ - IMPROVE: log messages do not display most specfic resolver name (IVY-170)
+ - IMPROVE: prints URL before downloading in verbose mode (IVY-257)
+ - IMPROVE: incorrect value in status attribute causes silent failure (IVY-259)
+ - IMPROVE: suport empty dependencies tag in an ivy file (IVY-281)
+ - IMPROVE: isolate dependency resolution from artifact downloading (IVY-254)
+ - IMPROVE: Pass artifact to repository when calling "put" (IVY-192)
+ - IMPROVE: Do not publish ivy file with bad revision, and allow to force the deliver when calling publish task (IVY-245)
+
+ - FIX: Problem with multiple artifact includes in transitive dependencies (IVY-283)
+ - FIX: Endless recursion in report (IVY-284)
+ - FIX: http url lister doesn't work when link text has spaces (IVY-282)
+ - FIX: Incorrect ant log level (IVY-279)
+ - FIX: Wrong resolution of dependencies if artifacts specified explicitly (IVY-261)
+ - FIX: Multiple versions of dependencies appearing in retrieve (IVY-264)
+ - FIX: Too many false CircularDependencyException errors thrown (IVY-230)
+ - FIX: CircularDependencyException not always thrown (IVY-184)
+ - FIX: NullPointer in BasicResolver (IVY-258)
+ - FIX: Bad diagnostics message when no space left (IVY-250)
+ - FIX: Maven2 POM support can find groupId from "parent" element (IVY-262)
+ - FIX: Parent version is expected to be equal to the module version in POM (IVY-241)
+ - FIX: problem with cache and returnFirst (IVY-207)
+ - FIX: modules splitted across a chain are not handled correctly (IVY-206)
+ - FIX: problem with conf extension and latest revisions (IVY-240)
+ - FIX: The clean-cache target in /src/example/hello-ivy/build.xml file refers to ${user.home}/.ivy-cache instead of ${user.home}/.ivy/cache/ (IVY-265)
+
+* thanks to Ivy Community:
+ - NEW: SSH Resolver added and aligned with SFTP resolver (IVY-273) (thanks to Andreas Sahlbach)
+ - NEW: ability to turn off transitivity at configuration level (IVY-103) (thanks to Karl Baum and Maarten Coene)
+ - NEW: a conflict manager that is able to allow implementation changes but not api changes (1.2.x - OK), (1.x.x - Not OK) (IVY-223) (thanks to Anders Janmyr)
+ - NEW: enhance standalone mode to execute java program by creating classloader of dependant jars from cache (IVY-210) (thanks to Peter Hayes)
+ - NEW: addition of Vfs Resolver which uses Commons-Vfs to resolve files (IVY-128) (thanks to Glen Marchesani, Matt Inger and Stephen Nesbitt)
+
+ - IMPROVE: use global properties in the recursive delivery (IVY-222) (with the contribution of Roshan Punnoose)
+ - IMPROVE: better handling of authentication (thanks to Christian Riege)
+
+ - FIX: Ant log messsages not embedded in task log (IVY-280) (thanks to Gilles Scokart)
+ - FIX: Ivy fails when downloading from a server that supports NTLM authentication (IVY-213) (thanks to Damon Rand)
+ - FIX: Delivered Ivy files with incomplete last line. (IVY-125) (thanks to Matthias Kilian)
+ - FIX: the vfs resolver should not log passwords (IVY-292) (thanks to Antoine Levy-Lambert)
+
+* thanks to Maarten Coene:
+ - NEW: add failureproperty parameter to the resolve task (IVY-285)
+ - NEW: Add type filtering to retrieve task (IVY-260)
+ - NEW: Add selectors to the configuration mapping (IVY-253)
+ - NEW: Add Ant task to retrieve information from an Ivy file without doing a resolve (IVY-255)
+ - NEW: add option to cachepath task to create a path with local artifact paths (IVY-221)
+ - NEW: allow extending configurations to override the mapping of their super configurations (IVY-218)
+
+ - IMPROVE: Retain artifact filenames along the publish/resolve/retrieve process (IVY-54)
+ - IMPROVE: report Ant-task doesn't process the reports in batch (IVY-247)
+ - IMPROVE: make ReportOutputter pluggable and customizable (IVY-205)
+ - IMPROVE: add wildcard support for extending configurations (IVY-235)
+ - IMPROVE: add support for xslt parameters in the report task (IVY-227)
+ - IMPROVE: comments now aren't lost when delivering ivy files (IVY-226)
+ - IMPROVE: add sort of 'fallback'-mapping to the defaultconfmapping attribute (IVY-215)
+ - IMPROVE: artifact origin is not included in the default report (IVY-251)
+
+ - FIX: VFS Resolve fails when trying to resolve a + version (IVY-237)
+ - FIX: report Ant-task doesn't use outputpattern for generating graphml reports (IVY-246)
+ - FIX: report Ant-task doesn't call init() on the internal XSLTProcess (IVY-248)
+ - FIX: value of confmappingoverride from imported configurations is lost when writing Ivy file (IVY-239)
+ - FIX: including configurations doesn't import the confmappingoverride setting (IVY-238)
+ - FIX: NullPointerException when the creation of Ivy file in cache fails (IVY-234)
+ - FIX: Ivy file containing 2 different versions of the same module is not deliverd correctly (IVY-229)
+ - FIX: ModuleRevisionId encode/decode doesn't work if revision is empty (IVY-233)
+ - FIX: cachepath task should preserve the order of the dependencies (IVY-225)
+ - FIX: specifying a defaultconfmapping adds dependencies of each unlisted configuration (IVY-214)
+
+* thanks to Johan Stuyts:
+ - NEW: always update artifacts when revision matches a regex pattern (IVY-189)
+ - NEW: provide Ant task for generating report about artifacts depended upon (IVY-194)
+
+ - IMPROVE: change default cache artifact pattern to handle missing extension (IVY-196)
+
+* thanks to Karl Baum:
+ - NEW: "this" symbol for configuration mappings (IVY-183)
+
+ - IMPROVE: performances improved (IVY-187)
+</code>
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC2.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC2.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC2.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4-RC2.html Mon Dec 18 09:06:07 2006
@@ -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: 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="./visit.php?url=./downloads/ivy/1.4-RC2/ivy-1.4-RC2-bin.zip">binaries</a></li>
+<li><a href="./visit.php?url=./downloads/ivy/1.4-RC2/ivy-1.4-RC2-src.zip">sources</a></li>
+<li><a href="./visit.php?url=./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>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.1.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.1.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.1.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.1.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,38 @@
+<!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: 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="./visit.php?url=./downloads/ivy/1.4.1/ivy-1.4.1-bin.zip">ivy-1.4.1-bin.zip</a>
+<a href="./visit.php?url=./downloads/ivy/1.4.1/ivy-1.4.1-src.zip">ivy-1.4.1-src.zip</a>
+<a href="./visit.php?url=./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.<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>
Added: incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/releasenotes/1.4.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,320 @@
+<!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: 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="./visit.php?url=./downloads/ivy/1.4/ivy-1.4-bin.zip">ivy-1.4-bin.zip</a>
+<a href="./visit.php?url=./downloads/ivy/1.4/ivy-1.4-src.zip">ivy-1.4-src.zip</a>
+<a href="./visit.php?url=./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 <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>
+</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#extra.html">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#event.html">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.conf.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.conf.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>
Added: incubator/ivy/trunk/src/doc/xooki/doc/resolver/chain.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/resolver/chain.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/resolver/chain.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/resolver/chain.html Mon Dec 18 09:06:07 2006
@@ -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: 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.conf.dir}/1/[organisation]/[module]/ivys/ivy-[revision].xml"/>
+ <artifact pattern="${ivy.conf.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.conf.dir}/1/[organisation]/[module]/ivys/ivy-[revision].xml"/>
+ <artifact pattern="${ivy.conf.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.conf.dir}/1/[organisation]/[module]/ivys/ivy-[revision].xml"/>
+ <artifact pattern="${ivy.conf.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>
Added: incubator/ivy/trunk/src/doc/xooki/doc/resolver/dual.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/resolver/dual.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/resolver/dual.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/resolver/dual.html Mon Dec 18 09:06:07 2006
@@ -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: 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>
Added: incubator/ivy/trunk/src/doc/xooki/doc/resolver/filesystem.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/resolver/filesystem.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/resolver/filesystem.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/resolver/filesystem.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,50 @@
+<!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: 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 [ivy: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>
Added: incubator/ivy/trunk/src/doc/xooki/doc/resolver/ibiblio.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/resolver/ibiblio.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/resolver/ibiblio.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/resolver/ibiblio.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,49 @@
+<!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: 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>
Added: incubator/ivy/trunk/src/doc/xooki/doc/resolver/ivyrep.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/resolver/ivyrep.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/resolver/ivyrep.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/resolver/ivyrep.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,51 @@
+<!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: 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">ivyrep</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 <a href="../../ivyrep.html">ivyrep</a> to find ivy files and ibiblio to find artifacts.
+However it can be configured to use other similar repositories.
+
+<i>Note that if no ivy file is found on ivyrep, then this resolver behaves like ibiblio resolver. Thus it's usually better to use this resolver instead of ibiblio one, which is provided mainly for compatibility reasons.</i>
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+<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>ivyroot</td><td>the root of the ivy repository.</td>
+ <td>No, defaults to ${ivy.ivyrep.default.ivy.root}</td></tr>
+ <tr><td>ivypattern</td><td>a pattern describing the layout of the ivy repository.</td>
+ <td>No, defaults to ${ivy.ivyrep.default.ivy.pattern}</td></tr>
+ <tr><td>artroot</td><td>the root of the artifacts repository.</td>
+ <td>No, defaults to ${ivy.ivyrep.default.artifact.root}</td></tr>
+ <tr><td>artpattern</td><td>a pattern describing the layout of the artifacts repository.</td>
+ <td>No, defaults to ${ivy.ivyrep.default.artifact pattern}</td></tr>
+</tbody>
+</table>
+<h1>Examples</h1>
+<code type="xml">
+<ivyrep name="ivyrep" />
+</code>
+A default ivyrep resolver, looking for ivy files on ivyrep and artifacts on ibiblio.
+
+<hr/>
+<code type="xml">
+<ivyrep name="ivyrep" ivyroot="http://ivyrep.mycompany.com"/>
+</code>
+Looks for ivy files on and ivyrep like web site located at http://ivyrep.mycompany.com.
+
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/resolver/sftp.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/resolver/sftp.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/resolver/sftp.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/resolver/sftp.html Mon Dec 18 09:06:07 2006
@@ -0,0 +1,103 @@
+<!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: 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">sftp</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 can be used when your ivy repository is located on a server accessible via sftp. The secured nature of sftp and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
+
+If your server supports ssh but not sftp, there is also an <a href="../../doc/resolver/ssh.html">ssh resolver</a>.
+
+Note that sftp is also supported by vfs, so you can use a vfs resolver instead. The advantage of this resolver is that you have a better control over authentication, it can prompt for username/password credentials, or you can use private/public key authentication, which is not possible with the vfs resolver. When it prompts for username/password, it uses a Swing dialog, which is not possible in a headless environment. If you want to prompt for the credentials on the command line, use ant input task for example before calling ivy.
+
+All necessary connection parameters can be set here via attributes.
+However all attributes defined in the pattern url of the resolver will have higher priority and will overwrite the values given here. To specify connection parameters in the pattern, you have to specify a full url and not just a path as pattern.
+e.g. pattern="/path/to/my/repos/[artifact].[ext]" will use all connection parameters from this class
+e.g. pattern="sftp://myserver.com/path/to/my/repos/[artifact].[ext]" will use all parameters from the attributes with the exception of the host, which will be "myserver.com"
+e.g. pattern="sftp://user:geheim@myserver.com:8022/path/to/my/repos/[artifact].[ext]" will use only the keyFile and keyFilePassword from the attributes (if needed). Rest will come from the url.
+
+
+Note that the authentication features of this resolver are exactly the same as the ssh resolver. Choosing between the two is often a matter of server implementation. If your server supports sftp, usually it's preferrable.
+
+Internally this resolver relies on <a href="http://www.jcraft.com/jsch/">jsch</a> as ssh client, which is a popular java ssh client, used for example in eclipse.
+
+<h1>Attributes</h1>
+This resolver shares the <a href="../../doc/configuration/resolvers#common.html">common attributes</a> of standard resolvers.
+<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>user</td><td>The username to provide as credential</td>
+ <td>No, defaults to username given on the patterns, or prompt if none is set</td></tr>
+ <tr><td>userPassword</td><td>The password to provide as credential</td>
+ <td>No, defaults to password given on the patterns, or prompt if none is set</td></tr>
+ <tr><td>keyFile</td><td>Path to the keyfile to use for authentication</td>
+ <td>No, defaults to username/password authentication</td></tr>
+ <tr><td>keyFilePassword</td><td>the password used to protect the key file</td>
+ <td>No, will prompt for password if keyFile authentication is used and if it is password encrypted</td></tr>
+ <tr><td>host</td><td>The host to connect to</td>
+ <td>No, defaults to host given on the patterns, fail if none is set</td></tr>
+ <tr><td>port</td><td>The port to connect to</td>
+ <td>No, defaults to 22</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>
+
+<h1>Example</h1>
+<code type="xml">
+<sftp user="myuser" host="myhost.com">
+ <ivy pattern="/path/to/ivy/[module]/ivy.xml"/>
+ <artifact pattern="/path/to/[organisation]/[module]/[artifact].[ext]"/>
+</sftp>
+</code>
+Will connect to myhost.com using myuser and prompt for the password.
+<hr/>
+<code type="xml">
+<sftp user="${myuser}" userPassword="${my.password}" host="myhost.com">
+ <ivy pattern="path/to/ivy/[module]/ivy.xml"/>
+ <artifact pattern="path/to/[organisation]/[module]/[artifact].[ext]"/>
+</sftp>
+</code>
+Will connect to myhost.com using user and password provided with ivy variables.
+<hr/>
+<code type="xml">
+<sftp>
+ <ivy pattern="sftp://user:geheim@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
+ <artifact pattern="sftp://user:secret@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
+</sftp>
+</code>
+Will connect to yourserver.com on port 8022 with user 'user' and password 'geheim' for authentication for ivy files, and to myserver.com on port 8022 using user 'user' and password 'secret' for the artifacts.
+<hr/>
+<code type="xml">
+<sftp keyFile="path/to/key/file" keyFilePassword="${password}">
+ <ivy pattern="sftp://user@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
+ <artifact pattern="sftp://user@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
+</sftp>
+</code>
+Will connect to yourserver.com on port 8022 with user 'user' and use keyFile path/to/key/file for keyFile and the value of password variable for keyFilePassword authentication for ivy files, and to myserver.com on port 8022 using user 'user' with the same keyFile/keyFilePassword pair for the artifacts.
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>
Added: incubator/ivy/trunk/src/doc/xooki/doc/resolver/ssh.html
URL: http://svn.apache.org/viewvc/incubator/ivy/trunk/src/doc/xooki/doc/resolver/ssh.html?view=auto&rev=488342
==============================================================================
--- incubator/ivy/trunk/src/doc/xooki/doc/resolver/ssh.html (added)
+++ incubator/ivy/trunk/src/doc/xooki/doc/resolver/ssh.html Mon Dec 18 09:06:07 2006
@@ -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: 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">ssh</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 can be used when your ivy repository is located on a server accessible via ssh. The secured nature of ssh and its wide spread implementation on most *nix servers makes this resolver a very good candidate in an enterprise environment. <span class="since">since 1.4</span>
+
+If your server supports sftp, you can consider using the <a href="../../doc/resolver/sftp.html">sftp resolver</a>.
+
+Internally this resolver shares most of its behaviour with the <a href="../../doc/resolver/sftp.html">sftp resolver</a>, so refer to its documentation for details.
+<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>user</td><td>The username to provide as credential</td>
+ <td>No, defaults to username given on the patterns, or prompt if none is set</td></tr>
+ <tr><td>userPassword</td><td>The password to provide as credential</td>
+ <td>No, defaults to password given on the patterns, or prompt if none is set</td></tr>
+ <tr><td>keyFile</td><td>Path to the keyfile to use for authentication</td>
+ <td>No, defaults to username/password authentication</td></tr>
+ <tr><td>keyFilePassword</td><td>the password used to protect the key file</td>
+ <td>No, will prompt for password if keyFile authentication is used and if it is password encrypted</td></tr>
+ <tr><td>host</td><td>The host to connect to</td>
+ <td>No, defaults to host given on the patterns, fail if none is set</td></tr>
+ <tr><td>port</td><td>The port to connect to</td>
+ <td>No, defaults to 22</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>
+
+<h1>Example</h1>
+<code type="xml">
+<ssh user="myuser" host="myhost.com">
+ <ivy pattern="/path/to/ivy/[module]/ivy.xml"/>
+ <artifact pattern="/path/to/[organisation]/[module]/[artifact].[ext]"/>
+</ssh>
+</code>
+Will connect to myhost.com using myuser and prompt for the password.
+<hr/>
+<code type="xml">
+<ssh keyFile="path/to/key/file" keyFilePassword="${password}">
+ <ivy pattern="ssh://user:geheim@yourserver.com:8022/path/to/repos/[module]/[revision]/ivy.xml"/>
+ <artifact pattern="ssh://user:geheim@myserver.com:8022/path/to/my/repos/[artifact].[ext]"/>
+</ssh>
+</code>
+Will connect to yourserver.com on port 8022 with user geheim and use keyFile path/to/key/file for keyFile and the value of password variable for keyFilePassword authentication for ivy files, and to myserver.com on port 8022 using user geheim with the same keyFile/keyFilePassword pair for the artifacts.
+
+ </textarea>
+<script type="text/javascript">xooki.postProcess();</script>
+</body>
+</html>