It looks like this is already done: the rc1 jars (incl the ones in apache-log4j-2.0-rc1-osgi-bin.zip) are all named 2.0-rc1, but the manifest has entries like: Bundle-Version: 2.0.0.rc1 Export-Package: org.apache.logging.log4j.core.async;version="2.0.0.rc1" Fragment-Host: org.apache.logging.log4j-api;bundle-version=2.0.0.rc1
This looks like what you had in mind, right? Sent from my iPhone > On 2014/02/20, at 7:20, Matt Sicker <[email protected]> wrote: > > Checks the manifest. In the Export-Package attribute, each package is paired > with a version number. Those are the version numbers used by OSGi, so I'd > assume they can differ from the jar name. > > >> On 19 February 2014 16:07, Remko Popma <[email protected]> wrote: >> Do OSGi containers look at the jar name or at the manifest for version info? >> >> Sent from my iPhone >> >> On 2014/02/20, at 1:31, Matt Sicker <[email protected]> wrote: >> >>> Just a quick follow-up to making things nice for the bundles. Version >>> numbers in OSGi are in the format: "major.minor.micro.thing" where the >>> major.minor.micro is the usual semantic versioning separated by dots, and >>> the last part can be a string like "rc1" or "beta-2" or "GA" or whatever as >>> is commonly done by many projects. By following the proper versioning >>> scheme, consumers of these bundles can specify a version range such as >>> [2.0, 2.1) so that all 2.0.x versions are considered, but not 2.1.x. >>> >>> Overall, this isn't too different (if at all) from common practices for >>> versioning, but it's nice to keep in mind if you guys don't like increasing >>> the minor version very often. >>> >>> -- >>> Matt Sicker <[email protected]> > > > > -- > Matt Sicker <[email protected]>
