On Mar 7, 2008, at 1:04 PM, Jacek Laskowski wrote:
On Thu, Mar 6, 2008 at 8:42 PM, Guillaume Nodet <[EMAIL PROTECTED]>
wrote:
I think the issue will persist for the release somehow.
If the release is labelled 3.0, the OSGi version would still be
3.0.0, as afaik,
OSGi versions always have 3 digits.
OSGi spec page 27:
3.2.1.17 Bundle-Version: 1.1
The Bundle-Version header specifies the version of this bundle. See
Version on page 28. The default value is 0.0.0
and on the page 28:
Version specifications are used in several places. A version token has
the following
grammar:
version ::=
major( '.' minor ( '.' micro ( '.' qualifier )? )? )?
major ::= number // See 1.3.2
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.
It means 3.0 is legal, isn't it? I'm fine with it for now, but when I
get more accustomed with the OSGi stuff I'm going to fix it.
It looks like 3.0 is legal but 3.0-SNAPSHOT would not since you have
to have a micro version to use a qualifier. Also the separator
between micro and qualifier must be be "." (and not "-" as everyone
use).
So when we release 3.0 we could make the OSGi version 3.0.
-dain
