Ivy Chinese Reference Document (4)-Key concepts (next)

Ivy introduced some of its own concepts to understand and ignore these concepts for Ivy's learning to use is helpful. Here translation of the official website of the main concept of Ivy article, the original text in this: http://ant.apache.org/ivy/history/2.1.0-rc1/concept.html

Split because the content is too long, here is the second part:

Six. Conflict Manager

The conflict Manager can select the revisions that need to be retained in the conflicting module revisions list.

If the revision corresponds to the same module, for example the same organization/module name pair, then the revised list of conflicts is called.

The list of available conflict managers can be obtained on the Conflict Manager page.

For more details about configuring the conflict Manager, see the conflict section of the Ivy file reference.

Seven. Pattern matcher mode Matching

Since 1.3 in many places Ivy uses patterns to match a range of objects. For example, when you declare a dependency by using a pattern that matches all the modules that you want to exclude, you can eliminate the multiple modules immediately.

Ivy uses a pluggable pattern-matching device to match which object names. The default definitions are 3:

* Exact

This is Matcher matches only if they are equal to the pattern one

This match matches only the strings, and the requirements are the same as the pattern.

* RegExp

This match allows you to use regular expressions supported by the java1.4 or later version of the pattern class

* Glob

This match allows you to use a Unix-style glob match, and the only characters you can use are matching the * of any string and matching a single character exactly? Note that the Jakarta can only be used when the oro2.0.8 is in Classpath.

Also note that in any match, the character ' * ' has a special meaning that matches any object. This is especially useful for default values that do not depend on a match.

Eight. Additional properties

After version 1.4, several tags in ivy's XML file can be extended by something called an attached property. The idea is simple: if you need more information to define your module, you can add the attributes you need and then access it as you would access other properties, such as in your schema.

After version 2.0, you can and recommend that you use the XML namespace for your attached properties. Using Ivy to attach namespaces is the easiest way to add your own attachment attributes.

For example:

Here is a ivy file with the attribute ' color ' set to blue:

<ivy-module　version="2.0"　xmlns:e="http://ant.apache.org/ivy/extra">
　　　　 <info　organisation="apache"
　　　　　　　　　　　 module="foo"
　　　　　　　　　　　 e:color="blue"
　　　　　　　　　　　 status="integration"
　　　　　　　　　　　 revision="1.59"
　　　　 />
　　　　 </ivy-module>