Property changes on: . ___________________________________________________________________ Modified: svn:ignore - ivy reports config.extra.js + ivy reports config.extra.js .project Index: concept.html =================================================================== --- concept.html (revision 675803) +++ concept.html (working copy) @@ -245,13 +245,13 @@ -While there is always only one resolution cache, you can [[configuration/caches define multiple repository caches]], each [[configuration/resolvers resolver]] being able to use a separate cache. +While there is always only one resolution cache, you can [[settings/caches define multiple repository caches]], each [[settings/resolvers resolver]] being able to use a separate cache.

Change management

To optimize the dependency resolution and the way the cache is used, Ivy assumes by default that a revision never changes. So once Ivy has a module in its cache (metadata and artifacts), it trusts the cache and do not even query the repository. This optimization is very useful in most cases, and causes no problem as long as you respect this paradigm: a revision never changes. Besides performance, there are several [[bestpractices good reasons]] to follow this principle. @@ -264,7 +264,7 @@

Changes in artifacts

Some people, especially those coming from maven 2 land, like to use one special revision to handle often updated modules. In maven 2 this is called a SNAPSHOT version, and some argue that it helps saves disk space to keep only one version for the high number of intermediary builds you can make whilst developing. -Ivy supports this kind of approach with the notion of changing revision. A changing revision is just that: a revision for which Ivy should consider that the artifacts may change over time. To handle this, you can either specify a dependency as changing on the [[ivyfile/dependency]] tag, or use the changingPattern and changingMatcher attributes on your [[configuration/resolvers]] to indicate which revision or group of revisions should be considered as changing. +Ivy supports this kind of approach with the notion of changing revision. A changing revision is just that: a revision for which Ivy should consider that the artifacts may change over time. To handle this, you can either specify a dependency as changing on the [[ivyfile/dependency]] tag, or use the changingPattern and changingMatcher attributes on your [[settings/resolvers]] to indicate which revision or group of revisions should be considered as changing. Once Ivy knows that a revision is changing, it will follow this principle to avoid checking your repository too often: if the module metadata has not changed, it will considered the whole module (including artifacts) as not changed. Even if the module descriptor file has changed, it will check the publication data of the module to see if this is a new publication of the same revision or not. Then if the publication date has changed, it will check the artifacts last modified timestamps, and download them accordingly. Index: configuration.html =================================================================== --- configuration.html (revision 675803) +++ configuration.html (working copy) @@ -22,135 +22,13 @@ + - + Index: configuration/caches.html =================================================================== --- configuration/caches.html (revision 675803) +++ configuration/caches.html (working copy) @@ -22,71 +22,13 @@ + - + Index: configuration/caches/cache.html =================================================================== --- configuration/caches/cache.html (revision 675803) +++ configuration/caches/cache.html (working copy) @@ -22,67 +22,13 @@ + - + Index: configuration/caches/ttl.html =================================================================== --- configuration/caches/ttl.html (revision 675803) +++ configuration/caches/ttl.html (working copy) @@ -22,48 +22,12 @@ + - Index: configuration/classpath.html =================================================================== --- configuration/classpath.html (revision 675803) +++ configuration/classpath.html (working copy) @@ -22,50 +22,12 @@ + - Index: configuration/conf.html =================================================================== --- configuration/conf.html (revision 675803) +++ configuration/conf.html (working copy) @@ -22,58 +22,12 @@ + - Index: configuration/conflict-managers.html =================================================================== --- configuration/conflict-managers.html (revision 675803) +++ configuration/conflict-managers.html (working copy) @@ -22,46 +22,12 @@ + - Index: configuration/include.html =================================================================== --- configuration/include.html (revision 675803) +++ configuration/include.html (working copy) @@ -22,55 +22,12 @@ + - Index: configuration/latest-strategies.html =================================================================== --- configuration/latest-strategies.html (revision 675803) +++ configuration/latest-strategies.html (working copy) @@ -22,69 +22,12 @@ + - Index: configuration/lock-strategies.html =================================================================== --- configuration/lock-strategies.html (revision 675803) +++ configuration/lock-strategies.html (working copy) @@ -22,41 +22,13 @@ + - + Index: configuration/macrodef.html =================================================================== --- configuration/macrodef.html (revision 675803) +++ configuration/macrodef.html (working copy) @@ -22,130 +22,12 @@ + - Index: configuration/macrodef/attribute.html =================================================================== --- configuration/macrodef/attribute.html (revision 675803) +++ configuration/macrodef/attribute.html (working copy) @@ -22,27 +22,13 @@ + - + Index: configuration/module.html =================================================================== --- configuration/module.html (revision 675803) +++ configuration/module.html (working copy) @@ -22,89 +22,12 @@ + - Index: configuration/modules.html =================================================================== --- configuration/modules.html (revision 675803) +++ configuration/modules.html (working copy) @@ -22,30 +22,12 @@ + - Index: configuration/namespace.html =================================================================== --- configuration/namespace.html (revision 675803) +++ configuration/namespace.html (working copy) @@ -22,106 +22,12 @@ + - Index: configuration/namespace/dest.html =================================================================== --- configuration/namespace/dest.html (revision 675803) +++ configuration/namespace/dest.html (working copy) @@ -22,42 +22,13 @@ + - + Index: configuration/namespace/fromtosystem.html =================================================================== --- configuration/namespace/fromtosystem.html (revision 675803) +++ configuration/namespace/fromtosystem.html (working copy) @@ -22,26 +22,13 @@ + - + Index: configuration/namespace/rule.html =================================================================== --- configuration/namespace/rule.html (revision 675803) +++ configuration/namespace/rule.html (working copy) @@ -22,28 +22,13 @@ + - + Index: configuration/namespace/src.html =================================================================== --- configuration/namespace/src.html (revision 675803) +++ configuration/namespace/src.html (working copy) @@ -22,28 +22,13 @@ + - + Index: configuration/namespaces.html =================================================================== --- configuration/namespaces.html (revision 675803) +++ configuration/namespaces.html (working copy) @@ -22,37 +22,12 @@ + - Index: configuration/outputters.html =================================================================== --- configuration/outputters.html (revision 675803) +++ configuration/outputters.html (working copy) @@ -22,44 +22,12 @@ + - Index: configuration/parsers.html =================================================================== --- configuration/parsers.html (revision 675803) +++ configuration/parsers.html (working copy) @@ -22,32 +22,12 @@ + - Index: configuration/properties.html =================================================================== --- configuration/properties.html (revision 675803) +++ configuration/properties.html (working copy) @@ -22,30 +22,12 @@ + - Index: configuration/property.html =================================================================== --- configuration/property.html (revision 675803) +++ configuration/property.html (working copy) @@ -22,40 +22,12 @@ + - Index: configuration/resolvers.html =================================================================== --- configuration/resolvers.html (revision 675803) +++ configuration/resolvers.html (working copy) @@ -22,175 +22,12 @@ + - Index: configuration/status.html =================================================================== --- configuration/status.html (revision 675803) +++ configuration/status.html (working copy) @@ -22,27 +22,12 @@ + - Index: configuration/statuses.html =================================================================== --- configuration/statuses.html (revision 675803) +++ configuration/statuses.html (working copy) @@ -22,51 +22,12 @@ + - Index: configuration/triggers.html =================================================================== --- configuration/triggers.html (revision 675803) +++ configuration/triggers.html (working copy) @@ -22,290 +22,13 @@ + - + Index: configuration/typedef.html =================================================================== --- configuration/typedef.html (revision 675803) +++ configuration/typedef.html (working copy) @@ -22,26 +22,12 @@ + - Index: configuration/version-matchers.html =================================================================== --- configuration/version-matchers.html (revision 675803) +++ configuration/version-matchers.html (working copy) @@ -22,30 +22,12 @@ + - Property changes on: images ___________________________________________________________________ Added: svn:ignore + Thumbs.db Index: index.html =================================================================== --- index.html (revision 675803) +++ index.html (working copy) @@ -71,7 +71,7 @@
  • [[reference]]
    • 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). +It's also in the reference doc that you will find all you always dreamed to know about ivy settings, ivy files, and ivy use (especially with ant).
  • [[dev]]
    • The developers's doc is useful for users who would like to extend Ivy or build it from source. It's also the documentation used by the Ivy team, so you will also find information about how we make releases. Index: ivyfile/conf.html =================================================================== --- ivyfile/conf.html (revision 675803) +++ ivyfile/conf.html (working copy) @@ -25,9 +25,9 @@ + + + Index: settings/caches.html =================================================================== --- settings/caches.html (revision 0) +++ settings/caches.html (revision 0) @@ -0,0 +1,92 @@ + + + + + + + + + + + + + Index: settings/caches/cache.html =================================================================== --- settings/caches/cache.html (revision 0) +++ settings/caches/cache.html (revision 0) @@ -0,0 +1,88 @@ + + + + + + + + + + + + + Index: settings/caches/ttl.html =================================================================== --- settings/caches/ttl.html (revision 0) +++ settings/caches/ttl.html (revision 0) @@ -0,0 +1,70 @@ + + + + + + + + + + + + + Index: settings/classpath.html =================================================================== --- settings/classpath.html (revision 0) +++ settings/classpath.html (revision 0) @@ -0,0 +1,72 @@ + + + + + + + + + + + + + Index: settings/conflict-managers.html =================================================================== --- settings/conflict-managers.html (revision 0) +++ settings/conflict-managers.html (revision 0) @@ -0,0 +1,68 @@ + + + + + + + + + + + + + Index: settings/include.html =================================================================== --- settings/include.html (revision 0) +++ settings/include.html (revision 0) @@ -0,0 +1,77 @@ + + + + + + + + + + + + + Index: settings/latest-strategies.html =================================================================== --- settings/latest-strategies.html (revision 0) +++ settings/latest-strategies.html (revision 0) @@ -0,0 +1,91 @@ + + + + + + + + + + + + + Index: settings/lock-strategies.html =================================================================== --- settings/lock-strategies.html (revision 0) +++ settings/lock-strategies.html (revision 0) @@ -0,0 +1,62 @@ + + + + + + + + + + + + + Index: settings/macrodef.html =================================================================== --- settings/macrodef.html (revision 0) +++ settings/macrodef.html (revision 0) @@ -0,0 +1,152 @@ + + + + + + + + + + + + + Index: settings/macrodef/attribute.html =================================================================== --- settings/macrodef/attribute.html (revision 0) +++ settings/macrodef/attribute.html (revision 0) @@ -0,0 +1,48 @@ + + + + + + + + + + + + + Index: settings/module.html =================================================================== --- settings/module.html (revision 0) +++ settings/module.html (revision 0) @@ -0,0 +1,111 @@ + + + + + + + + + + + + + Index: settings/modules.html =================================================================== --- settings/modules.html (revision 0) +++ settings/modules.html (revision 0) @@ -0,0 +1,52 @@ + + + + + + + + + + + + + Index: settings/namespace.html =================================================================== --- settings/namespace.html (revision 0) +++ settings/namespace.html (revision 0) @@ -0,0 +1,128 @@ + + + + + + + + + + + + + Index: settings/namespace/dest.html =================================================================== --- settings/namespace/dest.html (revision 0) +++ settings/namespace/dest.html (revision 0) @@ -0,0 +1,63 @@ + + + + + + + + + + + + + Index: settings/namespace/fromtosystem.html =================================================================== --- settings/namespace/fromtosystem.html (revision 0) +++ settings/namespace/fromtosystem.html (revision 0) @@ -0,0 +1,47 @@ + + + + + + + + + + + + + Index: settings/namespace/rule.html =================================================================== --- settings/namespace/rule.html (revision 0) +++ settings/namespace/rule.html (revision 0) @@ -0,0 +1,49 @@ + + + + + + + + + + + + + Index: settings/namespace/src.html =================================================================== --- settings/namespace/src.html (revision 0) +++ settings/namespace/src.html (revision 0) @@ -0,0 +1,49 @@ + + + + + + + + + + + + + Index: settings/namespaces.html =================================================================== --- settings/namespaces.html (revision 0) +++ settings/namespaces.html (revision 0) @@ -0,0 +1,59 @@ + + + + + + + + + + + + + Index: settings/outputters.html =================================================================== --- settings/outputters.html (revision 0) +++ settings/outputters.html (revision 0) @@ -0,0 +1,66 @@ + + + + + + + + + + + + + Index: settings/parsers.html =================================================================== --- settings/parsers.html (revision 0) +++ settings/parsers.html (revision 0) @@ -0,0 +1,54 @@ + + + + + + + + + + + + + Index: settings/properties.html =================================================================== --- settings/properties.html (revision 0) +++ settings/properties.html (revision 0) @@ -0,0 +1,52 @@ + + + + + + + + + + + + + Index: settings/property.html =================================================================== --- settings/property.html (revision 0) +++ settings/property.html (revision 0) @@ -0,0 +1,62 @@ + + + + + + + + + + + + + Index: settings/resolvers.html =================================================================== --- settings/resolvers.html (revision 0) +++ settings/resolvers.html (revision 0) @@ -0,0 +1,197 @@ + + + + + + + + + + + + + Index: settings/settings.html =================================================================== --- settings/settings.html (revision 0) +++ settings/settings.html (revision 0) @@ -0,0 +1,80 @@ + + + + + + + + + + + + + Index: settings/status.html =================================================================== --- settings/status.html (revision 0) +++ settings/status.html (revision 0) @@ -0,0 +1,49 @@ + + + + + + + + + + + + + Index: settings/statuses.html =================================================================== --- settings/statuses.html (revision 0) +++ settings/statuses.html (revision 0) @@ -0,0 +1,73 @@ + + + + + + + + + + + + + Index: settings/triggers.html =================================================================== --- settings/triggers.html (revision 0) +++ settings/triggers.html (revision 0) @@ -0,0 +1,311 @@ + + + + + + + + + + + + + Index: settings/typedef.html =================================================================== --- settings/typedef.html (revision 0) +++ settings/typedef.html (revision 0) @@ -0,0 +1,48 @@ + + + + + + + + + + + + + Index: settings/version-matchers.html =================================================================== --- settings/version-matchers.html (revision 0) +++ settings/version-matchers.html (revision 0) @@ -0,0 +1,52 @@ + + + + + + + + + + + + + Index: terminology.html =================================================================== --- terminology.html (revision 675803) +++ terminology.html (working copy) @@ -117,7 +117,7 @@ A module configuration is a way to use or construct a module. If the same module has different dependencies based on how it's used, those distinct dependency-sets are called its configurations in Ivy. Some modules may be used in different ways (think about hibernate which can be used inside or outside an application server), and this way may alter the artifacts you need (in the case of hibernate, jta.jar is needed only if it is used outside an application server). -Moreover, a module may need some other modules and artifacts only at build time, and some others at runtime. All those differents ways to use or build a module are called in ivy configurations. +Moreover, a module may need some other modules and artifacts only at build time, and some others at runtime. All those differents ways to use or build a module are called module configurations in ivy. For more details on configurations and how they are used in ivy, please refer to the main concepts page.

    Ivy Settings

    Index: toc.json =================================================================== --- toc.json (revision 675803) +++ toc.json (working copy) @@ -52,7 +52,7 @@ }, { "id":"tutorial/conf", - "title":"Using Ivy Configurations", + "title":"Using Ivy Module Configurations", "children": [ ] @@ -140,68 +140,68 @@ ] }, { - "id":"configuration", + "id":"settings", "title":"Settings Files", "children": [ { - "id":"configuration/property", + "id":"settings/property", "title":"property", "children": [ ] }, { - "id":"configuration/properties", + "id":"settings/properties", "title":"properties", "children": [ ] }, { - "id":"configuration/conf", + "id":"settings/settings", "title":"settings", "children": [ ] }, { - "id":"configuration/include", + "id":"settings/include", "title":"include", "children": [ ] }, { - "id":"configuration/classpath", + "id":"settings/classpath", "title":"classpath", "children": [ ] }, { - "id":"configuration/typedef", + "id":"settings/typedef", "title":"typedef", "children": [ ] }, { - "id":"configuration/lock-strategies", + "id":"settings/lock-strategies", "title":"lock-strategies", "children": [ ] }, { - "id":"configuration/caches", + "id":"settings/caches", "title":"caches", "children": [ { - "id":"configuration/caches/cache", + "id":"settings/caches/cache", "title":"cache", "children": [ { - "id":"configuration/caches/ttl", + "id":"settings/caches/ttl", "title":"ttl", "children": [ @@ -212,44 +212,44 @@ ] }, { - "id":"configuration/latest-strategies", + "id":"settings/latest-strategies", "title":"latest-strategies", "children": [ ] }, { - "id":"configuration/parsers", + "id":"settings/parsers", "title":"parsers", "children": [ ] }, { - "id":"configuration/namespaces", + "id":"settings/namespaces", "title":"namespaces", "children": [ { - "id":"configuration/namespace", + "id":"settings/namespace", "title":"namespace", "children": [ { - "id":"configuration/namespace/rule", + "id":"settings/namespace/rule", "title":"rule", "children": [ { - "id":"configuration/namespace/fromtosystem", + "id":"settings/namespace/fromtosystem", "title":"fromsystem / tosystem", "children": [ { - "id":"configuration/namespace/src", + "id":"settings/namespace/src", "title":"src", "children": [ ] }, { - "id":"configuration/namespace/dest", + "id":"settings/namespace/dest", "title":"dest", "children": [ @@ -264,11 +264,11 @@ ] }, { - "id":"configuration/macrodef", + "id":"settings/macrodef", "title":"macrodef", "children": [ { - "id":"configuration/macrodef/attribute", + "id":"settings/macrodef/attribute", "title":"attribute", "children": [ @@ -277,7 +277,7 @@ ] }, { - "id":"configuration/resolvers", + "id":"settings/resolvers", "title":"resolvers", "children": [ { @@ -353,18 +353,18 @@ ] }, { - "id":"configuration/conflict-managers", + "id":"settings/conflict-managers", "title":"conflict-managers", "children": [ ] }, { - "id":"configuration/modules", + "id":"settings/modules", "title":"modules", "children": [ { - "id":"configuration/module", + "id":"settings/module", "title":"module", "children": [ @@ -373,18 +373,18 @@ ] }, { - "id":"configuration/outputters", + "id":"settings/outputters", "title":"outputters", "children": [ ] }, { - "id":"configuration/statuses", + "id":"settings/statuses", "title":"statuses", "children": [ { - "id":"configuration/status", + "id":"settings/status", "title":"status", "children": [ @@ -393,14 +393,14 @@ ] }, { - "id":"configuration/triggers", + "id":"settings/triggers", "title":"triggers", "children": [ ] }, { - "id":"configuration/version-matchers", + "id":"settings/version-matchers", "title":"version-matchers", "children": [ Index: tutorial.html =================================================================== --- tutorial.html (revision 675803) +++ tutorial.html (working copy) @@ -51,9 +51,9 @@ a very first step toward using Ivy in a multi project environment.
  • [[tutorial/multiproject]]
    • a more complex example demonstrating the use of Ant+Ivy in a multi project environment. -
  • Using Ivy Configurations
    • +
  • [[tutorial/conf]]
    • show how to use configurations in ivy file to define set of artifacts. -
  • Building a repository
    • +
  • [[tutorial/build-repository]]
    • show how to build your own enterprise repository. Index: tutorial/build-repository.html =================================================================== --- tutorial/build-repository.html (revision 675803) +++ tutorial/build-repository.html (working copy) @@ -29,7 +29,7 @@ Fortunately the [[ant:install]] task is here to help: you can use specific settings for your repository maintenance build which will be used to maintain your target enterprise repository. These settings will point to another repository (for instance the maven 2 public repository) so that you will just have to ask Ivy to install the modules you want with a simple command line. -To demonstrate this we will first use some basic ivy settings files to show how it works, and then we will use the advanced [[configuration/namespaces]] feature to demonstrate how to deal with naming mismatch between the source and target repository. +To demonstrate this we will first use some basic ivy settings files to show how it works, and then we will use the advanced [[settings/namespaces]] feature to demonstrate how to deal with naming mismatch between the source and target repository.

    The project used

    The project that we will use is pretty simple. Index: tutorial/build-repository/advanced.html =================================================================== --- tutorial/build-repository/advanced.html (revision 675803) +++ tutorial/build-repository/advanced.html (working copy) @@ -35,7 +35,7 @@ This problem is pretty usual when you have an existing repository, and want to benefit from a large public repositories which do not follow the same naming conventions. Or simply because you find the public repository you use as a basis is not consistent enough - why all apache commons module aren't don't use the org.apache.commons organization? For historical reasons. But if you setup your own repository you may not want to suffer from history. -Fortunately Ivy has a very powerful answer to this kind of problem: [[configuration/namespaces namespaces]]. +Fortunately Ivy has a very powerful answer to this kind of problem: [[settings/namespaces namespaces]].

    Using namespaces

    If you look at the repository built with the [[tutorial/build-repository/basic previous tutorial]], you will see exactly what we were talking about: all apache commons module use their own name as organization. Index: tutorial/build-repository/basic.html =================================================================== --- tutorial/build-repository/basic.html (revision 675803) +++ tutorial/build-repository/basic.html (working copy) @@ -28,7 +28,7 @@ In this first step we use the [[ant:install]] task to install modules from the maven 2 repository to a file system based repository. We first install a module with no dependency, then a module with its dependencies.

    Basic: ivysettings.xml file used

    -The ivy settings file that we will use is very simple here. It defines two resolvers, libraries and my-repository. The first one is used as the source, the second one as the destination. In a typical setup the second one would be configured using [[configuration:include included]] settings, used by the development team. +The ivy settings file that we will use is very simple here. It defines two resolvers, libraries and my-repository. The first one is used as the source, the second one as the destination. In a typical setup the second one would be configured using [[settings/include included]] settings, used by the development team. @@ -95,7 +95,7 @@ As you can see the installation has failed, if you look at the log you will see that there are missing artifacts on the source repository. This means that you will need to download those artifacts manually, and copy them to your destination repository to complete the installation. Fortunately Ivy use a best effort algorithm during install, so that you have everything installed but the missing artifacts. -You may also have notice that Ivy has installed 2 different revisions of commons-logging (1.0.2, 1.0.4). This is due to the fact that we use the "no conflict" [[configuration/conflict-managers conflict manager]] in the ivysettings file. +You may also have notice that Ivy has installed 2 different revisions of commons-logging (1.0.2, 1.0.4). This is due to the fact that we use the "no conflict" [[settings/conflict-managers conflict manager]] in the ivysettings file. We do not want to evict any modules because we are building our own repository. Indeed if we get both commons-logging 1.0.2 and 1.0.4 it's because some modules among the transitive dependencies of hibernate depend on 1.0.2 and other on 1.0.4. If we got only 1.0.4, the module depending on 1.0.2 would be inconsistent in your own repository (depending on a version you don't have installed). Thus developers using this module directly would run into a problem. Index: tutorial/conf.html =================================================================== --- tutorial/conf.html (revision 675803) +++ tutorial/conf.html (working copy) @@ -25,7 +25,7 @@ Index: tutorial/dependence.html =================================================================== --- tutorial/dependence.html (revision 675803) +++ tutorial/dependence.html (working copy) @@ -101,7 +101,7 @@ This tag only load some properties for the ivy process in the same manner as ant would do it.

    settings

    This tag is in charge of initializing some parameters for ivy process. The directory that ivy will use to cache artifacts will be in a sub directory called ivy-cache of the directory containing the ivysettings.xml file itself. -The second parameter, tells ivy to use a resolver called "libraries" as its default resolver. More information can be found in the [[configuration settings reference documentation]]. +The second parameter, tells ivy to use a resolver called "libraries" as its default resolver. More information can be found in the [[settings settings reference documentation]].

    resolvers

    This tag defines the resolvers to use. Here we have two resolvers defined: "projects" and "libraries". The filesystem resolver called "projects" is able to resolve the internal dependencies by locating them on the local filesystem. Index: use/buildlist.html =================================================================== --- use/buildlist.html (revision 675803) +++ use/buildlist.html (working copy) @@ -41,7 +41,7 @@ since 2.0 The root and leaf attributes can be a delimited list of modules to use as roots. These modules, and all their dependencies will be included in the build list. since 2.0 By default, all the modules included in a circular dependency are grouped together so that any dependency of any module in the loop will apear before the modules in the loop. This garantee that if there is a depedendency path between a module A and a module B (but no dependency path from B to A), B will alway apear before A even if A is included in a loop in the provided set of modules to sort. -Note that circular dependency can also trigger a failure depending on the value configured in the circularDependencyStrategy of your settings +Note that circular dependency can also trigger a failure depending on the value configured in the circularDependencyStrategy of your settings since 2.0 When you are specifying root or leaf modules you can limit the resulting list to only direct dependencies of the roots modules or to modules that directly depends on your leaf modules. Index: use/configure.html =================================================================== --- use/configure.html (revision 675803) +++ use/configure.html (working copy) @@ -28,7 +28,7 @@ (since 2.0) the configure task is deprecated. Use the setting declaration
    The configure task is used to configure ivy with an xml settings file.

    -See settings for details about the settings file itself.

    +See [[settings]] for details about the settings file itself.

    Note for developers:
    After the call to this task, a reference to the configured ivy instance used by all subsequent ant tasks is put in the ant project, under the id "ivy.instance".     Index: use/makepom.html =================================================================== --- use/makepom.html (revision 675803) +++ use/makepom.html (working copy) @@ -52,7 +52,7 @@ mapping - describes the mapping from an Ivy configuration to a POM scope.
    These elements takes two attributes: + describes the mapping from an Ivy module configuration to a Maven POM scope.
    These elements takes two attributes: 0..n Index: use/publish.html =================================================================== --- use/publish.html (revision 675803) +++ use/publish.html (working copy) @@ -31,7 +31,7 @@ All the artifacts must have been created before calling this task. It does not create the artifacts themselves, but expects to find them at the location indicated by the artifacts pattern. -The target repository is given through the name of a resolver declared in current ivy settings. See settings for details about resolver supporting artifact publishing. +The target repository is given through the name of a resolver declared in current ivy settings. See [[settings]] for details about resolver supporting artifact publishing. It also publishes the delivered ivy file (except if you don't want), and even deliver it, if it has not been done with a previous deliver call or if forcedeliver is set to true. That's why this task takes some parameters useful only for delivery. See the illustration below: @@ -58,7 +58,7 @@ updatetrue to update ivy file metadata (revision, branch, publication date and status) before publishing, false otherwise. This is usually not necessary when using deliver before publish. No. Defaults to false validatetrue to force ivy files validation against ivy.xsd, false to force no validation - No. Defaults to default ivy value (as configured in [[configuration settings file]]) + No. Defaults to default ivy value (as configured in [[settings settings file]]) replacedynamicrevtrue to replace dynmic revisions by static ones in the delivered file, false to avoid this replacement since 1.3 No. Defaults to true publishivyTrue to publish delivered ivy file, false otherwise Index: use/resolve.html =================================================================== --- use/resolve.html (revision 675803) +++ use/resolve.html (working copy) @@ -96,7 +96,7 @@

    Concurrency

    -During resolve, Ivy creates a file in the [[configuration/caches resolution cache]]. The creation of this file is not aimed to support concurrency, meaning that you can't have two concurrent resolve of the same module, in the same resolution cache, with the same resolveId. +During resolve, Ivy creates a file in the [[settings/caches resolution cache]]. The creation of this file is not aimed to support concurrency, meaning that you can't have two concurrent resolve of the same module, in the same resolution cache, with the same resolveId. Note for developers: After the call to this task, a reference to the module descriptor resolved is put in the ant project under the id "ivy.resolved.descriptor". @@ -115,7 +115,7 @@ refreshtrue to force Ivy to resolve dynamic revision in this resolve process, false to use cached resolved revision since 2.0No. defaults to false - resolveModethe resolve mode to use for this dependency resolution process since 2.0No. defaults to using the resolve mode set in the [[configuration settings]] + resolveModethe resolve mode to use for this dependency resolution process since 2.0No. defaults to using the resolve mode set in the [[settings settings]] inlinetrue to use inline mode, false to resolve an ivy file since 1.4No. defaults to false Index: use/settings.html =================================================================== --- use/settings.html (revision 675803) +++ use/settings.html (working copy) @@ -28,7 +28,7 @@ The settings declaration is used to configure ivy with an xml settings file. -See [[configuration Settings Files]] for details about the settings file itself.

    +See [[settings]] for details about the settings file itself.

    Multiple settings can be defined in a build script. Every task can reference its own settings. Property changes on: xooki\images ___________________________________________________________________ Added: svn:ignore + Thumbs.db