Code component as well as many other artifacts in the container can be versioned. This document explains the format and semantics of these versions and how they are referred.
Versions are on the form
version ::= major [ "." minor [ "." micro [ "." qualifier ]]]Where
microare integers and
qualifieris any string.
A version is appended to an id separated by a colon. In cases where a file is created for each component version, the colon is replaced by a dash in the file name.
Versions are ordered first by major, then minor, then micro and then
by doing a lexical ordering on the qualifier.
This means that
a:1 < a:1.0 < a:1.0.0 < a:1.1 < a:1.1.0 < a:2
Whenever component is referenced by id (in code or configuration),
a fully or partially specified version may be included in the reference
by using the form
Such references are resolved using the following rules:
ahaving these versions:
[1.1, 1.2, 1.2, 1.3.test, 2.0]
awill resolve to
a:1will resolve to
In some cases, there is a need for merging multiple references into one. An example is inheritance of chains of version references, where multiple inherited chains may reference the same component.
Two version references are said to be compatible if one is a prefix of the other. In this case the most specific version is used. If they are not compatible they are conflicting. Example:
<search> <searcher id="Searcher:2.3" class="com.yahoo.search.example.Searcher"/> <searcher id="Searcher:2.4" class="com.yahoo.search.example.Searcher"/> <chain id="parenta"> <searcher id="Searcher:2"></searcher> </chain> <chain id="parentb"> <searcher id="Searcher:2.3"></searcher> </chain> <chain id="parentc"> <searcher id="Searcher:2.4"></searcher> </chain> <!-- This chain will get Searcher:2.3 --> <chain id="childa" inherits="parenta parentb" /> <!-- Error, as Searcher:2.3 and Searcher:2.4 are conflicting --> <chain id="childb" inherits="parentb parentc" /> </search>