Re: bootFeature with leading zero in version does not get state STARTED

Hi Steven, Don’t get me wrong: it’s in the feature/osgi version parser (powered by Felix utils), not in the spec. http://docs.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html The spec allows leading 0, however, I think

Re: bootFeature with leading zero in version does not get state STARTED

Hi JB, Thanks for your response. I guess we'll have to change our versioning scheme then. Do you have a reference to the OSGi spec stating leading zeroes are not allowed ? I might have to convince some people ;-) Also, it would be convenient to have at least a WARN in the logging about this, it t

Re: bootFeature with leading zero in version does not get state STARTED

Hi Steven, I would consider as "works as designed" ;) The OSGi version parser expects "flat" versioning. Regards JB > Le 23 mai 2021 à 11:06, Steven Huypens a écrit : > > Hi All, > > When using a bootFeature with a leading zero in the version number (eg. > 1.01.1-SNAPSHOT), the feature gets

bootFeature with leading zero in version does not get state STARTED

Hi All, When using a bootFeature with a leading zero in the version number (eg. 1.01.1-SNAPSHOT), the feature gets state UNINSTALLED after starting Karaf. All my bundles are OK, it's only the state of the feature that seems wrong. When I remove the leading zero (1.1.1-SNAPSHOT), the feature gets s