Return-Path: X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CA0808318 for ; Thu, 1 Sep 2011 15:08:04 +0000 (UTC) Received: (qmail 13212 invoked by uid 500); 1 Sep 2011 15:08:04 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 13120 invoked by uid 500); 1 Sep 2011 15:08:04 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 13104 invoked by uid 99); 1 Sep 2011 15:08:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 15:08:04 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 15:07:45 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 9B7002388A1C for ; Thu, 1 Sep 2011 15:07:22 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1164105 [1/3] - in /ant/site/ivy/production/history/trunk: ./ configuration/ configuration/caches/ configuration/macrodef/ configuration/namespace/ dev/ images/ ivyfile/ osgi/ resolver/ settings/ settings/caches/ settings/macrodef/ setting... Date: Thu, 01 Sep 2011 15:07:14 -0000 To: notifications@ant.apache.org From: hibou@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20110901150722.9B7002388A1C@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: hibou Date: Thu Sep 1 15:07:08 2011 New Revision: 1164105 URL: http://svn.apache.org/viewvc?rev=1164105&view=rev Log: regeneration site Added: ant/site/ivy/production/history/trunk/resolver/updatesite.html (with props) Modified: ant/site/ivy/production/history/trunk/ant.html ant/site/ivy/production/history/trunk/bestpractices.html ant/site/ivy/production/history/trunk/book.html ant/site/ivy/production/history/trunk/concept.html ant/site/ivy/production/history/trunk/configuration.html ant/site/ivy/production/history/trunk/configuration/caches.html ant/site/ivy/production/history/trunk/configuration/caches/cache.html ant/site/ivy/production/history/trunk/configuration/caches/ttl.html ant/site/ivy/production/history/trunk/configuration/classpath.html ant/site/ivy/production/history/trunk/configuration/conf.html ant/site/ivy/production/history/trunk/configuration/conflict-managers.html ant/site/ivy/production/history/trunk/configuration/include.html ant/site/ivy/production/history/trunk/configuration/latest-strategies.html ant/site/ivy/production/history/trunk/configuration/lock-strategies.html ant/site/ivy/production/history/trunk/configuration/macrodef.html ant/site/ivy/production/history/trunk/configuration/macrodef/attribute.html ant/site/ivy/production/history/trunk/configuration/module.html ant/site/ivy/production/history/trunk/configuration/modules.html ant/site/ivy/production/history/trunk/configuration/namespace.html ant/site/ivy/production/history/trunk/configuration/namespace/dest.html ant/site/ivy/production/history/trunk/configuration/namespace/fromtosystem.html ant/site/ivy/production/history/trunk/configuration/namespace/rule.html ant/site/ivy/production/history/trunk/configuration/namespace/src.html ant/site/ivy/production/history/trunk/configuration/namespaces.html ant/site/ivy/production/history/trunk/configuration/outputters.html ant/site/ivy/production/history/trunk/configuration/parsers.html ant/site/ivy/production/history/trunk/configuration/properties.html ant/site/ivy/production/history/trunk/configuration/property.html ant/site/ivy/production/history/trunk/configuration/resolvers.html ant/site/ivy/production/history/trunk/configuration/status.html ant/site/ivy/production/history/trunk/configuration/statuses.html ant/site/ivy/production/history/trunk/configuration/triggers.html ant/site/ivy/production/history/trunk/configuration/typedef.html ant/site/ivy/production/history/trunk/configuration/version-matchers.html ant/site/ivy/production/history/trunk/dev.html ant/site/ivy/production/history/trunk/dev/makerelease.html ant/site/ivy/production/history/trunk/dev/updatesite.html ant/site/ivy/production/history/trunk/extend.html ant/site/ivy/production/history/trunk/images/logo.png ant/site/ivy/production/history/trunk/index.html ant/site/ivy/production/history/trunk/install.html ant/site/ivy/production/history/trunk/ivyfile.html ant/site/ivy/production/history/trunk/ivyfile/artifact-conf.html ant/site/ivy/production/history/trunk/ivyfile/artifact-exclude-conf.html ant/site/ivy/production/history/trunk/ivyfile/artifact-exclude.html ant/site/ivy/production/history/trunk/ivyfile/artifact.html ant/site/ivy/production/history/trunk/ivyfile/conf.html ant/site/ivy/production/history/trunk/ivyfile/configurations.html ant/site/ivy/production/history/trunk/ivyfile/conflict.html ant/site/ivy/production/history/trunk/ivyfile/conflicts.html ant/site/ivy/production/history/trunk/ivyfile/dependencies.html ant/site/ivy/production/history/trunk/ivyfile/dependency-artifact-conf.html ant/site/ivy/production/history/trunk/ivyfile/dependency-artifact.html ant/site/ivy/production/history/trunk/ivyfile/dependency-conf.html ant/site/ivy/production/history/trunk/ivyfile/dependency-include-conf.html ant/site/ivy/production/history/trunk/ivyfile/dependency-include.html ant/site/ivy/production/history/trunk/ivyfile/dependency.html ant/site/ivy/production/history/trunk/ivyfile/description.html ant/site/ivy/production/history/trunk/ivyfile/exclude.html ant/site/ivy/production/history/trunk/ivyfile/extends.html ant/site/ivy/production/history/trunk/ivyfile/include.html ant/site/ivy/production/history/trunk/ivyfile/info.html ant/site/ivy/production/history/trunk/ivyfile/ivyauthor.html ant/site/ivy/production/history/trunk/ivyfile/license.html ant/site/ivy/production/history/trunk/ivyfile/manager.html ant/site/ivy/production/history/trunk/ivyfile/mapped.html ant/site/ivy/production/history/trunk/ivyfile/override.html ant/site/ivy/production/history/trunk/ivyfile/publications.html ant/site/ivy/production/history/trunk/ivyfile/repository.html ant/site/ivy/production/history/trunk/moreexamples.html ant/site/ivy/production/history/trunk/osgi.html ant/site/ivy/production/history/trunk/osgi/eclipse-plugin.html ant/site/ivy/production/history/trunk/osgi/osgi-mapping.html ant/site/ivy/production/history/trunk/osgi/sigil.html ant/site/ivy/production/history/trunk/osgi/standard-osgi.html ant/site/ivy/production/history/trunk/osgi/target-platform.html ant/site/ivy/production/history/trunk/principle.html ant/site/ivy/production/history/trunk/reference.html ant/site/ivy/production/history/trunk/resolver/chain.html ant/site/ivy/production/history/trunk/resolver/dual.html ant/site/ivy/production/history/trunk/resolver/filesystem.html ant/site/ivy/production/history/trunk/resolver/ibiblio.html ant/site/ivy/production/history/trunk/resolver/ivyrep.html ant/site/ivy/production/history/trunk/resolver/mirrored.html ant/site/ivy/production/history/trunk/resolver/obr.html ant/site/ivy/production/history/trunk/resolver/packager.html ant/site/ivy/production/history/trunk/resolver/sftp.html ant/site/ivy/production/history/trunk/resolver/ssh.html ant/site/ivy/production/history/trunk/resolver/url.html ant/site/ivy/production/history/trunk/resolver/vfs.html ant/site/ivy/production/history/trunk/settings.html ant/site/ivy/production/history/trunk/settings/caches.html ant/site/ivy/production/history/trunk/settings/caches/cache.html ant/site/ivy/production/history/trunk/settings/caches/ttl.html ant/site/ivy/production/history/trunk/settings/classpath.html ant/site/ivy/production/history/trunk/settings/conflict-managers.html ant/site/ivy/production/history/trunk/settings/credentials.html ant/site/ivy/production/history/trunk/settings/include.html ant/site/ivy/production/history/trunk/settings/latest-strategies.html ant/site/ivy/production/history/trunk/settings/lock-strategies.html ant/site/ivy/production/history/trunk/settings/macrodef.html ant/site/ivy/production/history/trunk/settings/macrodef/attribute.html ant/site/ivy/production/history/trunk/settings/module.html ant/site/ivy/production/history/trunk/settings/modules.html ant/site/ivy/production/history/trunk/settings/namespace.html ant/site/ivy/production/history/trunk/settings/namespace/dest.html ant/site/ivy/production/history/trunk/settings/namespace/fromtosystem.html ant/site/ivy/production/history/trunk/settings/namespace/rule.html ant/site/ivy/production/history/trunk/settings/namespace/src.html ant/site/ivy/production/history/trunk/settings/namespaces.html ant/site/ivy/production/history/trunk/settings/outputters.html ant/site/ivy/production/history/trunk/settings/parsers.html ant/site/ivy/production/history/trunk/settings/properties.html ant/site/ivy/production/history/trunk/settings/property.html ant/site/ivy/production/history/trunk/settings/resolvers.html ant/site/ivy/production/history/trunk/settings/settings.html ant/site/ivy/production/history/trunk/settings/signers.html ant/site/ivy/production/history/trunk/settings/status.html ant/site/ivy/production/history/trunk/settings/statuses.html ant/site/ivy/production/history/trunk/settings/triggers.html ant/site/ivy/production/history/trunk/settings/typedef.html ant/site/ivy/production/history/trunk/settings/version-matchers.html ant/site/ivy/production/history/trunk/standalone.html ant/site/ivy/production/history/trunk/terminology.html ant/site/ivy/production/history/trunk/textual.html ant/site/ivy/production/history/trunk/tutorial.html ant/site/ivy/production/history/trunk/tutorial/build-repository.html ant/site/ivy/production/history/trunk/tutorial/build-repository/advanced.html ant/site/ivy/production/history/trunk/tutorial/build-repository/basic.html ant/site/ivy/production/history/trunk/tutorial/conf.html ant/site/ivy/production/history/trunk/tutorial/defaultconf.html ant/site/ivy/production/history/trunk/tutorial/dependence.html ant/site/ivy/production/history/trunk/tutorial/dual.html ant/site/ivy/production/history/trunk/tutorial/multiple.html ant/site/ivy/production/history/trunk/tutorial/multiproject.html ant/site/ivy/production/history/trunk/tutorial/start.html ant/site/ivy/production/history/trunk/use/artifactproperty.html ant/site/ivy/production/history/trunk/use/artifactreport.html ant/site/ivy/production/history/trunk/use/buildlist.html ant/site/ivy/production/history/trunk/use/buildnumber.html ant/site/ivy/production/history/trunk/use/buildobr.html ant/site/ivy/production/history/trunk/use/cachefileset.html ant/site/ivy/production/history/trunk/use/cachepath.html ant/site/ivy/production/history/trunk/use/cleancache.html ant/site/ivy/production/history/trunk/use/configure.html ant/site/ivy/production/history/trunk/use/convertmanifest.html ant/site/ivy/production/history/trunk/use/convertpom.html ant/site/ivy/production/history/trunk/use/deliver.html ant/site/ivy/production/history/trunk/use/findrevision.html ant/site/ivy/production/history/trunk/use/info.html ant/site/ivy/production/history/trunk/use/install.html ant/site/ivy/production/history/trunk/use/listmodules.html ant/site/ivy/production/history/trunk/use/makepom.html ant/site/ivy/production/history/trunk/use/postresolvetask.html ant/site/ivy/production/history/trunk/use/publish.html ant/site/ivy/production/history/trunk/use/report.html ant/site/ivy/production/history/trunk/use/repreport.html ant/site/ivy/production/history/trunk/use/resolve.html ant/site/ivy/production/history/trunk/use/resources.html ant/site/ivy/production/history/trunk/use/retrieve.html ant/site/ivy/production/history/trunk/use/settings.html ant/site/ivy/production/history/trunk/use/var.html ant/site/ivy/production/history/trunk/yed.html Modified: ant/site/ivy/production/history/trunk/ant.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/ant.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/ant.html (original) +++ ant/site/ivy/production/history/trunk/ant.html Thu Sep 1 15:07:08 2011 @@ -134,6 +134,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/bestpractices.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/bestpractices.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/bestpractices.html (original) +++ ant/site/ivy/production/history/trunk/bestpractices.html Thu Sep 1 15:07:08 2011 @@ -134,6 +134,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/book.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/book.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/book.html (original) +++ ant/site/ivy/production/history/trunk/book.html Thu Sep 1 15:07:08 2011 @@ -695,7 +695,7 @@ A dependency resolver is a pluggable cla
  • find dependencies' ivy files
  • download dependencies' artifacts
    • -The notion of artifact "downloading" is large: an artifact can be on a web site, or on the local file system of your machine. The download is thus the act of bring a file from a repository to the ivy cache.

    Moreover, the fact that it is the responsibility of the resolver to find ivy files and download artifacts helps to implement various resolving strategies.

    As you see, a dependency resolver can be thought of as a class responsible for describing a repository.

    If you want to see which resolvers are available in ivy, you can go to the corresponding configuration section.

    Module configurations explained

    +The notion of artifact "downloading" is large: an artifact can be on a web site, or on the local file system of your machine. The download is thus the act of bring a file from a repository to the ivy cache.

    Moreover, the fact that it is the responsibility of the resolver to find ivy files and download artifacts helps to implement various resolving strategies.

    As you see, a dependency resolver can be thought of as a class responsible for describing a repository.

    If you want to see which resolvers are available in ivy, you can go to the resolvers configuration page.

    Module configurations explained

    Module configurations are described in the terminology page as a way to use or construct a module. Configurations being a central part of Ivy, they need more explanations as a concept.

    When you define a way to use or construct a module, you are able to define which artifacts are published by this module in this configuration, and you are also able to define which dependencies are needed in this configuration.

    Moreover, because dependencies in ivy are expressed on modules and not on artifacts, it is important to be able to define which configurations of the dependency are required in the configuration you define of your module. That's what is called configuration mapping.

    If you use only simple modules and do not want to worry about configurations, you don't have to worry about them. They're still there under the hood because ivy can't work without configurations. But most of the time if you declare nothing, ivy assumes that the artifacts of your module are published in all configurations, and that all the dependencies' configurations are required in all c onfigurations. And it works in simple cases. But whenever you want to separate things within a module, or get more control over things published and get better dependencies resolution, configurations will meet most of your needs.

    For details on how to declare your module configurations, how to declare in which configuration your artifacts are published, and how to declare configuration mapping, please refer to ivy file documentation. The configurations tutorial is also a good place to go to learn more about this concept.

    Variables

    During configuration, ivy allows you to define what are called ivy variables. Ivy variables can be seen as ant properties, and are used in a very similar way. In particular, you use a properties tag in the configuration file to load a properties file containing ivy variables and their values.

    But the main differences between ant properties and ivy variables are that ivy variables can be overridden, whereas ant
    properties can't, and that they are defined in separate environments.

    Actually all ant properties are imported into ivy variables when the configuration is done (if you call ivy from ant).
    This means that if you define an ant property after the call to configure, it will not be available as an ivy variable.
    On the other hand, ivy variables are NOT exported to ant, thus if you define ivy variables in ivy, do not try to us e them as ant properties.

    To use ivy variables, you just have to follow the same syntax as for ant properties:
    ${variablename}
    where variablename is the name of the variable.

    Finally, it's also important to be aware of the time of substitution of variables. This substitution is done as soon as possible. This means that when ivy encounters a reference to a variable, it tries to substitute it if such a variable is defined. Consequently, any later modification of the variable will not alter the value already substituted.

    Moreover, in an ant environment, a bunch of variables are going to be set by default via the ant property file loading mechanism (actually they are first loaded as ant properties and then imported as ivy variables, see Ant Tasks), and even in the ant properties themselves there is going to be eager substitution on loading, effectively making it impossible to override some variable purely via the ivysettings.properties file. Some variables will really only be able to be overridden via ant properties because of this.

    Moreover, it's also important to understand the difference between ivy variables and ivy pattern tokens.
    See the Patterns chapter below for what pattern tokens are.

    Patterns

    @@ -723,8 +723,8 @@ Ivy often needs to know which revision b
  • latest-lexico
    • This compares the revisions as strings, using lexicographic order (the one used by the Java string comparison). -See also how to configure new latest strategies here.

    Conflict Manager

    -A conflict manager is able to select, among a list of module revisions in conflict, a list of revisions to keep.
    Yes, it can select a list of revisions, even if most conflict managers select only one revision.
    But in some cases you will need to keep several revisions, and load in separate class loaders, for example.

    A list of revisions is said to be in conflict if they correspond to the same module, i.e. the same organisation/module name couple.

    The list of available conflict managers is available on the conflict manager configuration page.

    For more details on how to setup your conflict managers by module, see the conflicts section in the ivy file reference.

    Pattern matcher

    +See also how to configure new latest strategies here.

    Conflict Manager

    +A conflict manager is able to select, among a list of module revisions in conflict, a list of revisions to keep.
    Yes, it can select a list of revisions, even if most conflict managers select only one revision.
    But in some cases you will need to keep several revisions, and load in separate class loaders, for example.

    A list of revisions is said to be in conflict if they correspond to the same module, i.e. the same organisation/module name couple.

    The list of available conflict managers is available on the conflict manager configuration page.

    For more details on how to setup your conflict managers by module, see the conflicts section in the ivy file reference.

    Pat tern matcher

    since 1.3 In several places Ivy uses a pattern to match a set of objects. For instance, you can exclude several modules at once when declaring a dependency by using a pattern matching all the modules to exclude.

    Ivy uses a pluggable pattern matcher to match those object names. 3 are defined by default:
      @@ -748,11 +748,11 @@ And you can define your repository patte ${repository.dir}/[organisation]/[module]/[color]/[revision]/[artifact].[ext] -Note that in patterns you must use the unqualified attribute name (no namespace prefix).

      If you don't want to use xml namespaces, it's possible but you will need to disable ivy file validation, since your files won't fulffill anymore the official ivy xsd. See the settings documentation to see how to disable validation.

      Checksums

      +Note that in patterns you must use the unqualified attribute name (no namespace prefix).

      If you don't want to use xml namespaces, it's possible but you will need to disable ivy file validation, since your files won't fulffill anymore the official ivy xsd. See the settings documentation to see how to disable validation.

      Checksums

      since 1.4 Ivy allows the use of checksums, also known as digests, to verify the correctness of a downloaded file.

      For the moment Ivy supports the md5 and sha1 algorithms.

      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 algorithms 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 an 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".

      If you want to change this default, you can set the variable ivy.checksums. Hence, to disable checksum validation you just have to set ivy.checksums to "".

      Events and Triggers

      since 1.4 -When Ivy performs the dependency resolution and some other tasks, it fires events before and after the most important steps. You can listen to these events using Ivy API, or you can even register a trigger to perform a particular action when a particular event occur.

      This is a particularly powerful and flexible feature which allows, for example, you to perform a build of a dependency just before it is resolved, or follow what's happening during the dependency resolution process accuratly, and so on.

      For more details about events and triggers, see the triggers documentation page in the configuration section of this documentation.

      Circular Dependencies

      +When Ivy performs the dependency resolution and some other tasks, it fires events before and after the most important steps. You can listen to these events using Ivy API, or you can even register a trigger to perform a particular action when a particular event occur.

      This is a particularly powerful and flexible feature which allows, for example, you to perform a build of a dependency just before it is resolved, or follow what's happening during the dependency resolution process accuratly, and so on.

      For more details about events and triggers, see the triggers documentation page in the configuration section of this documentation.

      Circular Dependencies

      since 1.4 Circular dependencies can be either direct or indirect. For instance, if A depends on A, it's a circular dependency, and if A depends on B which itself depends on A, this is also a circular dependency.

      Prior to Ivy 1.4 circular dependencies where causing a failure in Ivy. As of Ivy 1.4, the behaviour of Ivy when it finds a circular dependency is configurable through a circular dependency strategy.

      3 built-in strategies are available:
        @@ -761,7 +761,7 @@ Circular dependencies can be either dire
      • error
        • halt the dependency resolution when a circular dependency is found
      -See the configuration page to see how to configure the circular dependency strategy you want to use.

      Cache and Change Management

      +See the configuration page to see how to configure the circular dependency strategy you want to use.

      Cache and Change Management

      Ivy heavily relies on local caching to avoid accessing remote repositories too often, thus saving a lot of network bandwidth and time.

      Cache types

      An Ivy cache is composed of two different parts:
        @@ -852,7 +852,7 @@ As you can see, using text conventions i
        How does it work ?

        Now that you have been introduced to the main ivy terminology and concepts, it is time to give some explanation of how ivy works.

        Usual cycle of modules between different locations

        More details on ant tasks here.

        Configure

        -Ivy needs to be configured to be able to resolve your dependencies. This configuration is usually done with a settings file, which defines a set of dependency resolvers. Each resolver is able to find ivy files and/or artifacts, given simple information such as organisation, module, revision, artifact name, artifact type and artifact extension.

        The configuration is also responsible for indicating which resolver should be used to resolve which module. This configuration is dependent only on your environment, i.e. where the modules and artifacts can be found.

        A default configuration is used by ivy when none is given. This configuration uses ivyrep to resolve all modules.

        Resolve

        +Ivy needs to be configured to be able to resolve your dependencies. This configuration is usually done with a settings file, which defines a set of dependency resolvers. Each resolver is able to find ivy files and/or artifacts, given simple information such as organisation, module, revision, artifact name, artifact type and artifact extension.

        The configuration is also responsible for indicating which resolver should be used to resolve which module. This configuration is dependent only on your environment, i.e. where the modules and artifacts can be found.

        A default configuration is used by ivy when none is given. This configuration uses an ibiblio resolver pointing to http://repo1.maven.org/maven2/ to resolve all modules.

        Resolve

        The resolve time is the moment when ivy actually resolves the dependencies of one module. It first needs to access the ivy file of the module for which it resolves the dependencies.

        Then, for each dependency declared in this file, it asks the appropriate resolver (according to settings) to find the module (i.e. either an ivy file for it, or its artifacts if no ivy file can be found). It also uses a filesystem based cache to avoid asking for a dependency if it is already in cache (at least if possible, which is not the case with latest revisions).

        If the resolver is a composite one (i.e. a chain or a dual resolver), several resolvers may actually be called to find the module.

        When the dependency module has been found, its ivy file is downloaded to the ivy cache. Then ivy checks if the dependency module has dependencies, in which case it recursilvel y traverses the graph of dependencies.

        All over this traversal, conflict management is done to prevent access to a module as soon as possible.

        When ivy has traversed the whole graph, it asks the resolvers to download the artifacts corresponding to each of the dependencies which are not already in the cache and which have not been evicted by conflict managers. All downloads are made to the ivy cache.

        Finally, an xml report is generated in the cache, which allows ivy to easily know what are all the dependencies of a module, without traversing the graph again.

        After this resolve step, two main steps are possible: either build a path with artifacts in the cache, or copy them to another directory structure.

        Retrieve

        What is called retrieve in ivy is the act of copying artifacts from the cache to another directory structure. This is done using a pattern, which indicates to ivy where the files should be copied.

        For this, ivy uses the xml report in the cache corresponding to the module it should retrieve to know which artifacts should be copied.

        It also checks if the files are not already copied to maximize performances.

        Building a path from the cache

        In some cases, it is preferable to use artifacts directly from the cache. Ivy is able to use the xml report generated at resolve time to build a path of all artifacts required.

        This can be particularly useful when building plug-ins for IDEs.

        Reports

        @@ -1576,6 +1576,8 @@ Ivy comes with a set of built-in depende sftpStandardFinds ivy files and artifacts in any repository accessible with sftp. ChainCompositeDelegates the finding to a chain of sub resolvers. DualCompositeDelegates the finding of ivy files to one resolver and of artifacts to another. +OBRStandardResolve modules as OSGi bundles listed by an OSGi obr.xml. +Eclipse updatesiteStandardResolve modules as OSGi bundles which are hosted on an Eclipse update site. @@ -2363,6 +2365,10 @@ This resolver shares the -A local repository which is trusted to always provide correct dependency for the Import-Package requirements.
        Mirrored Resolver
        +A local repository which is trusted to always provide correct dependency for the Import-Package requirements.
        Eclipse updatesite
        + + + + +
        Tagupdatesite
        Handle latestyes
        Handle publishno
        + +since 2.3 + +This resolver is one of the resolver which supports         OSGi™ dependencies.
        It resolves modules (OSGi bundles) which are hosted in an Eclipse™ update site.

        This resolver supports old style Eclipse updatesite, based on simply a site.xml. It also supports Eclipse P2 repositories.

        Attributes

        +This resolver shares the common attributes of composite resolvers. + + + + + + + + + + + + + + +
        AttributeDescriptionRequired
        urlthe URL of the Eclipse updatesiteYes
        requirementStrategydefines how strict should be the OSGi resolution. Can be one of first or noambiguityNo, default to noambiguity
        metadataTtlthe time in milliseconds the updatesite metadata are considered up to dateNo, default to 3600000 (1 hour)
        forceMetadataUpdateforce the update of the updatesite metadata without checking their freshnessNo, default to false
        + +The requirement strategy is defining how the resolver should behave in front of several choices. In the OSGi dependency model, an Import-Package requirement can be satisfied by several different bundles. So when resolving such requirement, Ivy will first look into the already resolved bundles if one provides that package. If it fails to find one, then two behaviours can occur: +
          +
        • if the requirement strategy is first, among the bundles statifying the requirement, it will shoose the first one. A warn will be logged ahout the choice Ivy has to arbitrarily do.
          • +
        • if the requirement strategy is noambiguity, Ivy will make the resolution fail.
          • +
        + +

        Examples

        +
        +<updatesite name="ivyde-updatesite" url="http://www.apache.org/dist/ant/ivyde/updatesite" />
+
        +A simple repository configured to load the Apache IvyDE Eclipse update site.
        Mirrored Resolver
        @@ -2390,7 +2433,7 @@ A local repository which is trusted to a since 2.3
        -This resolver can resolve dependencies against sevrail mirror of the same repository. From a list of mirror urls, it will iteratively try to resolve the dependencies against each one.

        Attributes

        +This resolver can resolve dependencies against several mirrors of the same repository. From a list of mirror urls, it will iteratively try to resolve the dependencies against each one.

        Attributes

        This resolver shares the common attributes of standard resolvers.
        Tagmirroredurl
        Handle latestyes with http urls (and apache server) and with file urls, no with other urls
        @@ -2830,7 +2873,19 @@ Triggers an ant call of the target unzip Logs any successful artifact download, with information on the source and destination, and details on download size and duration.

        The file attribute is optional, the log trigger will output messages to console if it isn't provided.
        version-matchers

        Tag: version-matchers

        Defines a list of version matchers.since 1.4 -The child tag used for the version matcher must be equal to a name of a report outputter type (added with the typedef tag).

        A version matcher is used to evaluate if a dependency version constraint matches a dependency version.

        Child elements

        +The child tag used for the version matcher must be equal to a name of a report outputter type (added with the typedef tag).

        A version matcher is used to evaluate if a dependency version constraint matches a dependency version.

        Attributes

        +
        + + + + + + + + + +
        AttributeDescritionRequired
        usedefaultswhen set to true, includes the built-in version matchers (Latest, Sub Revision, and Version Ranger Matcher). Exact Revision Matcher is always includedNo, defaults to false
        +

        Child elements

        @@ -3008,7 +3063,8 @@ After the description, you can also plac - + +
        ElementDescriptionCardinality
        descriptionThe content of the info/description element is inherited from the parent.
        configurationsConfigurations defined in the parent descriptor are added to any configurations defined in the child descriptor.
        dependenciesDependencies defined in the parent descriptor are added to any dependencies defined in the child descriptor.
        allinfo, description, configurations, and dependencies from the parent descriptor are merged into the child descriptor.
        licensesLicenses defined in the parent descriptor are added to any licenses defined in the child descriptor.
        allinfo, description, configurations, licenses and dependencies from the parent descriptor are merged into the child descriptor.
        @@ -4722,6 +4778,7 @@ Available options are: checkIfChangedWhen set to true, the resolve will compare the result with the last resolution done on this module, with those configurations in order to define the property ivy.deps.changed. Put it to false may provides slightly better performance. (since 2.0)No, default to 'true' + useCacheOnlyWhen set to true, it forces the resolvers to only use their caches and not their actual contents.(since 2.0)No, default to 'false' Modified: ant/site/ivy/production/history/trunk/concept.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/concept.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/concept.html (original) +++ ant/site/ivy/production/history/trunk/concept.html Thu Sep 1 15:07:08 2011 @@ -134,6 +134,7 @@
      • ssh resolver
      • vfs
      • OSGi Bundle Repository
        • +
      • Eclipse updatesite
      • Mirrored Resolver
    • conflict-managers
      • @@ -237,7 +238,7 @@ A dependency resolver is a pluggable cla
    • find dependencies' ivy files
    • download dependencies' artifacts
    -The notion of artifact "downloading" is large: an artifact can be on a web site, or on the local file system of your machine. The download is thus the act of bring a file from a repository to the ivy cache.

    Moreover, the fact that it is the responsibility of the resolver to find ivy files and download artifacts helps to implement various resolving strategies.

    As you see, a dependency resolver can be thought of as a class responsible for describing a repository.

    If you want to see which resolvers are available in ivy, you can go to the corresponding configuration section.

    Module configurations explained

    +The notion of artifact "downloading" is large: an artifact can be on a web site, or on the local file system of your machine. The download is thus the act of bring a file from a repository to the ivy cache.

    Moreover, the fact that it is the responsibility of the resolver to find ivy files and download artifacts helps to implement various resolving strategies.

    As you see, a dependency resolver can be thought of as a class responsible for describing a repository.

    If you want to see which resolvers are available in ivy, you can go to the resolvers configuration page.

    Module configurations explained

    Module configurations are described in the terminology page as a way to use or construct a module. Configurations being a central part of Ivy, they need more explanations as a concept.

    When you define a way to use or construct a module, you are able to define which artifacts are published by this module in this configuration, and you are also able to define which dependencies are needed in this configuration.

    Moreover, because dependencies in ivy are expressed on modules and not on artifacts, it is important to be able to define which configurations of the dependency are required in the configuration you define of your module. That's what is called configuration mapping.

    If you use only simple modules and do not want to worry about configurations, you don't have to worry about them. They're still there under the hood because ivy can't work without configurations. But most of the time if you declare nothing, ivy assumes that the artifacts of your module are published in all configurations, and that all the dependencies' configurations are required in all c onfigurations. And it works in simple cases. But whenever you want to separate things within a module, or get more control over things published and get better dependencies resolution, configurations will meet most of your needs.

    For details on how to declare your module configurations, how to declare in which configuration your artifacts are published, and how to declare configuration mapping, please refer to ivy file documentation. The configurations tutorial is also a good place to go to learn more about this concept.

    Variables

    During configuration, ivy allows you to define what are called ivy variables. Ivy variables can be seen as ant properties, and are used in a very similar way. In particular, you use a properties tag in the configuration file to load a properties file containing ivy variables and their values.

    But the main differences between ant properties and ivy variables are that ivy variables can be overridden, whereas ant
    properties can't, and that they are defined in separate environments.

    Actually all ant properties are imported into ivy variables when the configuration is done (if you call ivy from ant).
    This means that if you define an ant property after the call to configure, it will not be available as an ivy variable.
    On the other hand, ivy variables are NOT exported to ant, thus if you define ivy variables in ivy, do not try to us e them as ant properties.

    To use ivy variables, you just have to follow the same syntax as for ant properties:
    ${variablename}
    where variablename is the name of the variable.

    Finally, it's also important to be aware of the time of substitution of variables. This substitution is done as soon as possible. This means that when ivy encounters a reference to a variable, it tries to substitute it if such a variable is defined. Consequently, any later modification of the variable will not alter the value already substituted.

    Moreover, in an ant environment, a bunch of variables are going to be set by default via the ant property file loading mechanism (actually they are first loaded as ant properties and then imported as ivy variables, see Ant Tasks), and even in the ant properties themselves there is going to be eager substitution on loading, effectively making it impossible to override some variable purely via the ivysettings.properties file. Some variables will really only be able to be overridden via ant properties because of this.

    Moreover, it's also important to understand the difference between ivy variables and ivy pattern tokens.
    See the Patterns chapter below for what pattern tokens are.

    Patterns

    @@ -265,8 +266,8 @@ Ivy often needs to know which revision b
  • latest-lexico
    • This compares the revisions as strings, using lexicographic order (the one used by the Java string comparison). -See also how to configure new latest strategies here.

    Conflict Manager

    -A conflict manager is able to select, among a list of module revisions in conflict, a list of revisions to keep.
    Yes, it can select a list of revisions, even if most conflict managers select only one revision.
    But in some cases you will need to keep several revisions, and load in separate class loaders, for example.

    A list of revisions is said to be in conflict if they correspond to the same module, i.e. the same organisation/module name couple.

    The list of available conflict managers is available on the conflict manager configuration page.

    For more details on how to setup your conflict managers by module, see the conflicts section in the ivy file reference.

    Pattern matcher

    +See also how to configure new latest strategies here.

    Conflict Manager

    +A conflict manager is able to select, among a list of module revisions in conflict, a list of revisions to keep.
    Yes, it can select a list of revisions, even if most conflict managers select only one revision.
    But in some cases you will need to keep several revisions, and load in separate class loaders, for example.

    A list of revisions is said to be in conflict if they correspond to the same module, i.e. the same organisation/module name couple.

    The list of available conflict managers is available on the conflict manager configuration page.

    For more details on how to setup your conflict managers by module, see the conflicts section in the ivy file reference.

    Pat tern matcher

    since 1.3 In several places Ivy uses a pattern to match a set of objects. For instance, you can exclude several modules at once when declaring a dependency by using a pattern matching all the modules to exclude.

    Ivy uses a pluggable pattern matcher to match those object names. 3 are defined by default:
      @@ -290,11 +291,11 @@ And you can define your repository patte ${repository.dir}/[organisation]/[module]/[color]/[revision]/[artifact].[ext] -Note that in patterns you must use the unqualified attribute name (no namespace prefix).

      If you don't want to use xml namespaces, it's possible but you will need to disable ivy file validation, since your files won't fulffill anymore the official ivy xsd. See the settings documentation to see how to disable validation.

      Checksums

      +Note that in patterns you must use the unqualified attribute name (no namespace prefix).

      If you don't want to use xml namespaces, it's possible but you will need to disable ivy file validation, since your files won't fulffill anymore the official ivy xsd. See the settings documentation to see how to disable validation.

      Checksums

      since 1.4 Ivy allows the use of checksums, also known as digests, to verify the correctness of a downloaded file.

      For the moment Ivy supports the md5 and sha1 algorithms.

      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 algorithms 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 an 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".

      If you want to change this default, you can set the variable ivy.checksums. Hence, to disable checksum validation you just have to set ivy.checksums to "".

      Events and Triggers

      since 1.4 -When Ivy performs the dependency resolution and some other tasks, it fires events before and after the most important steps. You can listen to these events using Ivy API, or you can even register a trigger to perform a particular action when a particular event occur.

      This is a particularly powerful and flexible feature which allows, for example, you to perform a build of a dependency just before it is resolved, or follow what's happening during the dependency resolution process accuratly, and so on.

      For more details about events and triggers, see the triggers documentation page in the configuration section of this documentation.

      Circular Dependencies

      +When Ivy performs the dependency resolution and some other tasks, it fires events before and after the most important steps. You can listen to these events using Ivy API, or you can even register a trigger to perform a particular action when a particular event occur.

      This is a particularly powerful and flexible feature which allows, for example, you to perform a build of a dependency just before it is resolved, or follow what's happening during the dependency resolution process accuratly, and so on.

      For more details about events and triggers, see the triggers documentation page in the configuration section of this documentation.

      Circular Dependencies

      since 1.4 Circular dependencies can be either direct or indirect. For instance, if A depends on A, it's a circular dependency, and if A depends on B which itself depends on A, this is also a circular dependency.

      Prior to Ivy 1.4 circular dependencies where causing a failure in Ivy. As of Ivy 1.4, the behaviour of Ivy when it finds a circular dependency is configurable through a circular dependency strategy.

      3 built-in strategies are available:
        @@ -303,7 +304,7 @@ Circular dependencies can be either dire
      • error
        • halt the dependency resolution when a circular dependency is found
      -See the configuration page to see how to configure the circular dependency strategy you want to use.

      Cache and Change Management

      +See the configuration page to see how to configure the circular dependency strategy you want to use.

      Cache and Change Management

      Ivy heavily relies on local caching to avoid accessing remote repositories too often, thus saving a lot of network bandwidth and time.

      Cache types

      An Ivy cache is composed of two different parts:
        Modified: ant/site/ivy/production/history/trunk/configuration.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration.html (original) +++ ant/site/ivy/production/history/trunk/configuration.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
      • ssh resolver
      • vfs
      • OSGi Bundle Repository
        • +
      • Eclipse updatesite
      • Mirrored Resolver
    • conflict-managers
      • Modified: ant/site/ivy/production/history/trunk/configuration/caches.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/caches.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/caches.html (original) +++ ant/site/ivy/production/history/trunk/configuration/caches.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
    • ssh resolver
    • vfs
    • OSGi Bundle Repository
      • +
    • Eclipse updatesite
    • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/caches/cache.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/caches/cache.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/caches/cache.html (original) +++ ant/site/ivy/production/history/trunk/configuration/caches/cache.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/caches/ttl.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/caches/ttl.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/caches/ttl.html (original) +++ ant/site/ivy/production/history/trunk/configuration/caches/ttl.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/classpath.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/classpath.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/classpath.html (original) +++ ant/site/ivy/production/history/trunk/configuration/classpath.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/conf.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/conf.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/conf.html (original) +++ ant/site/ivy/production/history/trunk/configuration/conf.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/conflict-managers.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/conflict-managers.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/conflict-managers.html (original) +++ ant/site/ivy/production/history/trunk/configuration/conflict-managers.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/include.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/include.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/include.html (original) +++ ant/site/ivy/production/history/trunk/configuration/include.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/latest-strategies.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/latest-strategies.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/latest-strategies.html (original) +++ ant/site/ivy/production/history/trunk/configuration/latest-strategies.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/lock-strategies.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/lock-strategies.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/lock-strategies.html (original) +++ ant/site/ivy/production/history/trunk/configuration/lock-strategies.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/macrodef.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/macrodef.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/macrodef.html (original) +++ ant/site/ivy/production/history/trunk/configuration/macrodef.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/macrodef/attribute.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/macrodef/attribute.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/macrodef/attribute.html (original) +++ ant/site/ivy/production/history/trunk/configuration/macrodef/attribute.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/module.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/module.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/module.html (original) +++ ant/site/ivy/production/history/trunk/configuration/module.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/modules.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/modules.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/modules.html (original) +++ ant/site/ivy/production/history/trunk/configuration/modules.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/namespace.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/namespace.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/namespace.html (original) +++ ant/site/ivy/production/history/trunk/configuration/namespace.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/namespace/dest.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/namespace/dest.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/namespace/dest.html (original) +++ ant/site/ivy/production/history/trunk/configuration/namespace/dest.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/namespace/fromtosystem.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/namespace/fromtosystem.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/namespace/fromtosystem.html (original) +++ ant/site/ivy/production/history/trunk/configuration/namespace/fromtosystem.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/namespace/rule.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/namespace/rule.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/namespace/rule.html (original) +++ ant/site/ivy/production/history/trunk/configuration/namespace/rule.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/namespace/src.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/namespace/src.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/namespace/src.html (original) +++ ant/site/ivy/production/history/trunk/configuration/namespace/src.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/namespaces.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/namespaces.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/namespaces.html (original) +++ ant/site/ivy/production/history/trunk/configuration/namespaces.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/outputters.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/outputters.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/outputters.html (original) +++ ant/site/ivy/production/history/trunk/configuration/outputters.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/parsers.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/parsers.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/parsers.html (original) +++ ant/site/ivy/production/history/trunk/configuration/parsers.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/properties.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/properties.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/properties.html (original) +++ ant/site/ivy/production/history/trunk/configuration/properties.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/property.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/property.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/property.html (original) +++ ant/site/ivy/production/history/trunk/configuration/property.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/resolvers.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/resolvers.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/resolvers.html (original) +++ ant/site/ivy/production/history/trunk/configuration/resolvers.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/status.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/status.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/status.html (original) +++ ant/site/ivy/production/history/trunk/configuration/status.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers
    • Modified: ant/site/ivy/production/history/trunk/configuration/statuses.html URL: http://svn.apache.org/viewvc/ant/site/ivy/production/history/trunk/configuration/statuses.html?rev=1164105&r1=1164104&r2=1164105&view=diff ============================================================================== --- ant/site/ivy/production/history/trunk/configuration/statuses.html (original) +++ ant/site/ivy/production/history/trunk/configuration/statuses.html Thu Sep 1 15:07:08 2011 @@ -135,6 +135,7 @@
  • ssh resolver
  • vfs
  • OSGi Bundle Repository
    • +
  • Eclipse updatesite
  • Mirrored Resolver
  • conflict-managers