...
I'm proposing the following implementation: GenericArtifactVersion.java (unit test: GenericArtifactVersionTest.java). It has been integrated in artifact 3.0-SNAPSHOT r656775(15/5/2008) as ComparableVersion.java.
Features:
- Mixing of '-' (dash) and '.' (dot) separators
- Transition between characters and digits also constitutes a separator:
Wiki Markup 1.0alpha1 => \[1, 0, alpha, 1\]; This fixes '1.0alpha10 < 1.0alpha2'
- Unlimited number of version components
- Version components in the text can be digits or strings
- strings are checked for well-known qualifiers and the qualifier ordering is used for version ordering
- well-known qualifiers (case insensitive)
- snapshot (NOTE; snapshot needs discussion)
- alpha or a
- beta or b
- milestone or m
- rc or cr
- (the empty string) or ga or final
- sp
- well-known qualifiers (case insensitive)
- version components prefixed with '-' will result in a sub-list of version components.
A dash usually precedes a qualifier, and is always less important than something preceded with a dot.
We need to somehow record the separators themselves, which is done by sublists.
Parse examples:Wiki Markup 1.0-alpha1 => \[1, 0, \["alpha", 1\]\]
Wiki Markup 1.0-rc-2 => \[1, 0, \["rc", \[2\]\]\]
...
- A POM change to support something like this to identify a version-scheme implementation artifact:
No Format <versionScheme> <groupId>..</groupId> <artifactId>..</artifactId> <version>..</version> <\!-\- we may need to disallow version ranges here \--> </versionScheme> - Maven-metadata at the artifact level needs to include the tag above. We'll limit version schemes on a per artifact basis. This is required in order to resolve versions using ranges.
- An interface definition for VersionScheme
- A way to detect what is the version class inside the version-scheme artifact; I hope we can use plexus, as long as multiple version-scheme implementations (same hint, same package/classname) can be accessed simultaneously without conflict.
- Refactoring the version code out of maven-artifact so plugin code etc. can use it too
- The super pom will contain a default versionScheme tag listing the maven internal implementation
...
As an example here's an XSD you could use to describe versions:
| No Format |
|---|
<xs:schema>
<xs:element name="versionSchemeDefinition">
<xs:complexType>
<xs:sequence>
<!-- the order of qualifierDefinitions is from oldest to newest -->
<xs:element ref="qualifierDefinition" minOccurs="0" maxOccurs="unbounded"/>
<xs:choice maxOccurs="unbounded" minOccurs="0">
<xs:element ref="stringComponent"/>
<xs:element ref="numberComponent"/>
<xs:element ref="subComponent"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="qualifierDefinition">
<xs:complexType>
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="caseSensitive" type="xs:boolean" default="false"/>
</xs:complexType>
</xs:element>
<xs:element name="stringComponent">
<xs:complexType>
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="prefix" type="xs:string" default="."/>
</xs:complexType>
</xs:element>
<xs:element name="numberComponent" type="xs:int">
<xs:complexType>
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="prefix" type="xs:string" default="."/>
<xs:attribute name="optional" type="xs:boolean" default="false"/>
</xs:complexType>
</xs:element>
<xs:element name="subComponent">
<xs:complexType>
<xs:choice maxOccurs="unbounded" minOccurs="0">
<xs:element ref="stringComponent"/>
<xs:element ref="numberComponent"/>
<xs:element ref="subComponent"/>
</xs:choice>
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="prefix" type="xs:string" default="-"/>
</xs:complexType>
</xs:element>
</xs:schema>
|
A sample scheme:
| No Format |
|---|
<versionSchemeDefinition>
<qualifierDefinition name="snapshot"/>
<qualifierDefinition name="alpha"/>
<qualifierDefinition name="beta"/>
<qualifierDefinition name="rc"/>
<qualifierDefinition name=""/>
<qualifierDefinition name="ga"/>
<qualifierDefinition name="sp"/>
<numberComponent name="major"/>
<numberComponent name="minor" optional="true"/>
<numberComponent name="micro" optional="true"/>
<stringComponent name="qualifier" optional="true"/>
<numberComponent name="buildnumber" optional="true"/>
</versionSchemeDefinition>
|
...
| Wiki Markup |
|---|
<ac:structured-macro ac:name="anchor" ac:schema-version="1" ac:macro-id="6e04eaffe3296db0-5b21c202-40a64525-8681bb56-f06ab36aa2b54418b1420f89"><ac:parameter ac:name="">osgi</ac:parameter></ac:structured-macro> \[0\] [OSGi Service Platform Release 4 Version 4.1 Core Specification|http://www.osgi.org/Release4/Download], §3.2.4 "Version" and §3.2.5 "Version Ranges" on page 38, §3.5.3 "Bundle-Version" on page 46, §6.1.26.5 "Version.compareTo()" on page 200 |