[
https://issues.apache.org/jira/browse/FELIX-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623121#action_12623121
]
rickhall edited comment on FELIX-682 at 8/16/08 6:50 AM:
----------------------------------------------------------------
Regardless, this is still a new feature or a wish, not a bug in Felix.
If we do decide to address this, Marcel's point is still correct, we have to
decide how we should set all of the various package information. For a package,
we can define spec title, spec version, spec vendor, impl title, impl version,
and impl vendor. Currently, Felix defines a package for every exported package
and assigned package name to spec title and the package version to spec
version. Does this even make sense?
For impl version, it sounds like you want it to be set to
Implementation-Version value, which isn't even related to OSGi metadata, so
would the same be true for Specification-Version?
Also, is this really something you want for 1.2.0? I am nearly to the point
where I want to freeze features for 1.2.0.
was (Author: rickhall):
Regardless, this is still a new feature or a wish, not a bug in Felix.
If we do decide to address this, Marcel's point is still correct, we have to
decide how we should set all of the various package information. For a package,
we can define spec title, spec version, spec vendor, impl title, impl version,
and impl vendor. Currently, Felix defines a package for every exported package
and assigned package name to spec title and the package version to spec
version. Does this even make sense?
For impl version, it sounds like you want it to be set to
Implementation-Version value, which isn't even related to OSGi metadata, so
would the same be true for Specification-Version?
> Package.getImplementationVersion returns null for package loaded by Felix
> -------------------------------------------------------------------------
>
> Key: FELIX-682
> URL: https://issues.apache.org/jira/browse/FELIX-682
> Project: Felix
> Issue Type: Wish
> Components: Framework
> Affects Versions: felix-1.0.4
> Environment: NA
> Reporter: Sahoo
> Fix For: felix-1.2.0
>
> Attachments: Felix-682.zip, java-pkg-versioning-spec-bug.zip
>
>
> Even though MANIFEST.MF has proper entry for Implementation-Version,
> Package.getImplementationVersion() returns null. A reproducible test case is
> attached. It is described below:
> public class Foo implements BundleActivator {
> public void start(BundleContext context) throws Exception {
> Package p = getClass().getPackage();
> System.out.println(p);
> System.out.println(p.getImplementationVersion());
> }
> }
> The headers for this bundle are:
> osgi-test1 (10)
> ---------------
> Tool = Bnd-0.0.255
> Bundle-Activator = sahoo.osgitest1.Foo
> Implementation-Version = 1.0-SNAPSHOT
> Implementation-Vendor-Id = sahoo
> Bundle-Version = 1.0.0.SNAPSHOT
> Build-Jdk = 1.5.0_13-rev
> Implementation-Title = osgi-test1
> Created-By = Apache Maven Bundle Plugin
> Bundle-ManifestVersion = 2
> Manifest-Version = 1.0
> Bnd-LastModified = 1218821794953
> Private-Package = sahoo.osgitest1
> Bundle-Name = osgi-test1
> Built-By = ss141213
> Import-Package = org.osgi.framework;version="1.3"
> Bundle-SymbolicName = sahoo.osgi-test1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
