Added: ant/ivy/site/target/history/2.2.0/settings/credentials.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/2.2.0/settings/credentials.html?rev=1005260&view=auto ============================================================================== --- ant/ivy/site/target/history/2.2.0/settings/credentials.html (added) +++ ant/ivy/site/target/history/2.2.0/settings/credentials.html Wed Oct 6 21:25:29 2010 @@ -0,0 +1,142 @@ + + + + + + + +credentials | Apache Ivy + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ +
+ +
+ + + + +
+ + +
+ + +
+ + + + + + + +
+
+ +

credentials

+
Tag: credentials

Configures HTTP authentication credentials. since 2.0.

Attributes

+ + + + + + + + + + + + + + +
AttributeDescriptionRequired
hostthe name of the hostYes
realmthe name of the realmNo
usernamethe usernameYes
passwdthe passwordYes
+ +
+
+ + + + + + + + + + + + +
+ + Added: ant/ivy/site/target/history/2.2.0/settings/include.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/2.2.0/settings/include.html?rev=1005260&view=auto ============================================================================== --- ant/ivy/site/target/history/2.2.0/settings/include.html (added) +++ ant/ivy/site/target/history/2.2.0/settings/include.html Wed Oct 6 21:25:29 2010 @@ -0,0 +1,153 @@ + + + + + + + +include | Apache Ivy + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ +
+ +
+ + + + +
+ + +
+ + +
+ + + + + + + +
+
+ +

include

+
Tag: include

Includes another ivysettings file as if it were part of this one. since 1.3 + +The included ivysettings file has to be a complete well formed ivysettings file, i.e. it does have to include the
<ivysettings>
tag.

Attributes

+ + + + + + + + + + +
AttributeDescriptionRequired
urla URL to the ivysettings file to includeYes, unless file is specified
filea path to the ivysettings file to includeYes, unless url is specified
+

Examples

+
+<ivysettings>
<property name="myrepository" value="path/to/my/real/rep"/>
<settings defaultResolver="default"/>
<include file="path/to/ivysettings-default.xml"/>
</ivysettings> +
+with ivysettings-default.xml: +
+<ivysettings>
<property name="myrepository" value="path/to/rep" overwrite="false"/>
<resolvers>
<ivyrep name="default" ivyroot="${myrepository}"/>
</resolvers>
</ivysettings> +
+ +The included ivysettings defines a resolver named default, which is an ivyrep resolver, with its root configured as being the value of myrepository variable. This variable is given the value path/to/rep in the included file, but because the attribute overwrite is set to false, it will not override the value given in the main ivysettings including this one, so the value used for myrepository will be path/to/my/real/rep.

+
+<ivysettings>
<include file="ivysettings-macro.xml"/>
<resolvers>
<mymacro name="includeworks" mymainrep="included/myrep" mysecondrep="included/secondrep"/>
</resolvers>
</ivysettings> +
+with ivysettings-macro.xml being the ivysettings example given on the macrodef documentation page.
This lets us easily reuse the custom macro resolver.
+
+
+ + + + + + + + + + + + +
+ + Added: ant/ivy/site/target/history/2.2.0/settings/latest-strategies.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/2.2.0/settings/latest-strategies.html?rev=1005260&view=auto ============================================================================== --- ant/ivy/site/target/history/2.2.0/settings/latest-strategies.html (added) +++ ant/ivy/site/target/history/2.2.0/settings/latest-strategies.html Wed Oct 6 21:25:29 2010 @@ -0,0 +1,159 @@ + + + + + + + +latest-strategies | Apache Ivy + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ +
+ +
+ + + + +
+ + +
+ + +
+ + + + + + + +
+
+ +

latest-strategies

+
Tag: latest-strategies

Defines a list of latest strategies usable in Ivy. Each latest strategy is identified by its name, given as an attribute.
The child tag used for the latest strategy must be equal to a name of a latest strategy type (usually added with the typedef tag).

The latest strategies which are included in Ivy by default are: +
    +
  • latest-time
  • compares the revisions date to know which is the latest. While this is often a good strategy in terms of pertinence, it's drawback is that it can be slow when dealing with remote repositories. If you use ivyrep,
    for example, Ivy has to ask the http server for the date of each ivy file before knowing which is the latest. +
  • latest-revision
  • compares the revisions as strings, using an algorithm close to the one used in php's version_compare function.
    This algorithm takes into account the special meaning of some text. For instance, with this strategy, 1.0-dev1 is considered before 1.0-alpha1, which in turn is before 1.0-rc1, which is before 1.0, which is before 1.0.1. +
  • latest-lexico
  • compares the revisions as strings, using lexicographic order (the one used by java string comparison). +
+ +

Child elements

+ + + + + + + + +
ElementDescriptionCardinality
any latest strategyadds a latest strategy to the list of available strategies0..n
+ +

latest-revision

+since 1.4 The latest-revision can now be configured to handle more words with special meanings than the one defined in php version_compare function.

Here is an example of how you can do so: +
+<latest-strategies>
<latest-revision name="mylatest-revision">
<specialMeaning name="PRE" value="-2"/>
<specialMeaning name="QA" value="4"/>
<specialMeaning name="PROD" value="5"/>
</latest-revision>
</latest-strategies> +
+Knowing that the default "special meaning" words are the following: +
+    <specialMeaning name="dev" value="-1"/>
<specialMeaning name="rc" value="1"/>
<specialMeaning name="final" value="2"/> +
+You can even remove or redefine the default special meanings by setting usedefaultspecialmeanings="false" on the latest-revision tag.
Example: +
+<latest-strategies>
<latest-revision name="mylatest-revision" usedefaultspecialmeanings="false">
<specialMeaning name="pre" value="-2"/>
<specialMeaning name="m" value="1"/>
<specialMeaning name="rc" value="2"/>
<specialMeaning name="prod" value="3"/>
</latest-revision>
</latest-strategies> +
+ + + +
+
+ + + + + + + + + + + + +
+ + Added: ant/ivy/site/target/history/2.2.0/settings/lock-strategies.html URL: http://svn.apache.org/viewvc/ant/ivy/site/target/history/2.2.0/settings/lock-strategies.html?rev=1005260&view=auto ============================================================================== --- ant/ivy/site/target/history/2.2.0/settings/lock-strategies.html (added) +++ ant/ivy/site/target/history/2.2.0/settings/lock-strategies.html Wed Oct 6 21:25:29 2010 @@ -0,0 +1,145 @@ + + + + + + + +lock-strategies | Apache Ivy + + + + + + + + + + +
+ + + + + + + + + + + + + +
+ +
+ +
+ + + + +
+ + +
+ + +
+ + + + + + + +
+
+ +

lock-strategies

+
Tag: lock-strategies since 2.0 + +Defines a list of lock strategies usable in Ivy. + +A lock strategy is used by a cache manager to decide when and how locking should be performed (see settings/cache to see how to configure the lock strategy to use).

Two lock strategies are registered by default: +
    +
  • no-lock
  • This lock strategy actually performs no locking at all, and thus should not be used in an environment where the cache is shared by multiple processes.

    This strategy is implemented by (NoLockStrategy)

    +
  • artifact-lock
  • This strategy acquires a lock whenever a module descriptor or an artifact is downloaded to the cache, which makes a good solution when you want to share your repository cache.

    Note that this strategy is based on file locking, performed by default using the java.io.File.createNewFile() atomicity (which is documented as atomic in the javadoc, but not recommended to perform locks). A java.nio.FileLock based implementation is also provided, but according to our tests the createNewFile based one performs better and more reliably. We heavily recommend making your own testing in your target environment before relying on this lock strategy for heavily concurrent operations.

    This strategy is implemented by (ArtifactLockStrategy) +
+ +The child tag used for the lock strategy must be equal to a name of a lock strategy type (added with the typedef tag).

Child elements

+ + + + + + + + +
ElementDescriptionCardinality
any lock strategyadds a lock strategy to the list of available ones0..n
+
+
+ + + + + + + + + + + + +
+ +