Le 26/10/14 21:13, Stefan Seelmann a écrit : > Hi Emmanuel, > > I removed it for now because Eclipse complained about the version "2.4" > of commons.io, the right OSGi version would be 2.4.0. I think that 2.4 will get extended automatically to 2.4.0. In fact, 2.4 stands for 2.4.* :
http://www.eclipse.org/virgo/documentation/virgo-documentation-3.6.0.M03/docs/virgo-user-guide/html/ch02s02.html "Package Version : Each exported package has a version. The exported package’s version may be specified on the Export-Package manifest header. For example Export-Package: org.foo;version="2.9",org.bar;version="1" exports two packages: |org.foo|, at version |2.9.0| and |org.bar|, at version |1.0.0|." > Also for > Import-Package it must be named "version", not "bundle-version" (in > valueeditor). My bad. > As far as I understand that named version is the minimum > version, not a fixed version. It can, we can also define a range, like [2.4,2.6] (which means all the versions between 2.4.0 and 2.6.N. > But I agree that a version makes sense, > I'd add them later when migration is done and all works fine. Okie, makes sense. At some point, I think we should have the Manifest containing meta-information, not real versions, otherwise it will be a real burden to update all the manifests which contain versions... I have no idea if it's possible though.
