Hello I'm "looking around" different fundamental packages (when working on pax-web R7 support) and I've found strange thing.
Ultimate source (i.e., OSGi Core specification R6 and R7) define this package: org.osg.framework.dto. - in R6, this package is specified at version "1.0" (in PDF) - in R7, this package is specified at version "1.1" (in PDF) This is fine - new packages introduced to Core do not start with their "parent" version: - in R6, org.osgi.framework package is at version 1.8 - in R7, org.osgi.framework package is at version 1.9 But, checking: - https://repo1.maven.org/maven2/org/osgi/osgi.core/6.0.0/osgi.core-6.0.0.jar (and felix-framework 5.6.x) - https://repo1.maven.org/maven2/org/osgi/osgi.core/7.0.0/osgi.core-7.0.0.jar (and felix-framework 6.0.x) I see "org.osgi.framework.dto" package (respectively): - in R6 it is Export-Package'd at version 1.8 - in R6, there's org/osgi/framework/dto/packageinfo file with "version 1.8" - in R6, this package has package-info.java with @org.osgi.annotation.versioning.Version("1.8") - in R7 it is Export-Package'd at version 1.8 (!) - in R7, this package has package-info.java with @org.osgi.annotation.versioning.Version("1.8") maven-bundle-plugin generates (logical) "org.osgi.framework.dto;version="[1.8,2)"" as import package for my bundle. Actually the same problem is in Equinox. So - where's the mistake? Why official osgi.core bundle exports org.osgi.framework.dto at wrong version? regards Grzegorz Grzybek
