"pgier" wrote :
| I don't understand enough about how OSGi works, but as a second option, can we
translate the maven version to something OSGi compatible in our builds? So maybe use the
maven standard versions in our poms, but then put the equivalent OSGi version string into
jar metadata, or somewhere else that it can be used?
The osgi versioning convention is simply what we describe as ours here:
. Its just two short
sections from the osgi r4 core spec:
"osgi 4.0.1 core spec" wrote :
| 3.2.4 Version
| Version specifications are used in several places. A version token has the following
| version ::=
| major( '.' minor ( '.' micro ( '.' qualifier )? )? )?
| major ::= number
| minor ::= number
| micro ::= number
| qualifier ::= ( alphanum | â_â | '-' )+
| A version token must not contain any white space. The default value for a
| version is 0.0.0.
| 3.2.5 Version Ranges
| A version range describes a range of versions using a mathematical interval notation.
See  Mathematical Convention for Interval Notation.
| The syntax of a version range is:
| version-range ::= interval | atleast
| interval ::= ( '[' | '(' ) floor ',' ceiling ( ']' |
| atleast ::= version
| floor ::= version
| ceiling ::= version
| If a version range is specified as a single version, it must be interpreted as the
range [version,â). The default for a non-specified version range is 0, which maps to
| Note that the use of a comma in the version range requires it to be enclosed in double
quotes. For example:
| Import-Package: com.acme.foo;version="[1.23, 2)",
| In the following table, for each specified range in the left-hand column, a
| version x is considered to be a member of the range if the predicate in the
| right-hand column is true.
| Table 2 Examples of version ranges
| Example Predicate
| [1.2.3, 4.5.6) 1.2.3 <= x < 4.5.6
| [1.2.3, 4.5.6] 1.2.3 <= x <= 4.5.6
| (1.2.3, 4.5.6) 1.2.3 < x < 4.5.6
| (1.2.3, 4.5.6] 1.2.3 < x <= 4.5.6
| 1.2.3 1.2.3 <= x
View the original post :
Reply to the post :