[jira] Resolved: (FELIX-897) Empty system package is exported when a semicolon is present in "extra" configuration

["Richard S. Hall (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FELIX-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall resolved FELIX-897.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: felix-1.6.0
         Assignee: Richard S. Hall

I have committed a patch against the manifest parser to check for empty package names in both imports and exports, which will catch the situation in the system bundle as well as an other installed bundle. Pierre, if you could verify the fix and then close this issue it would be great. Thanks for reporting it.

> Empty system package is exported when a semicolon is present in "extra" configuration
> -------------------------------------------------------------------------------------
>
>                 Key: FELIX-897
>                 URL: https://issues.apache.org/jira/browse/FELIX-897
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-1.4.0, felix-1.4.1
>         Environment: linux/jdk1.5
>            Reporter: Pierre De Rop
>            Assignee: Richard S. Hall
>            Priority: Minor
>             Fix For: felix-1.6.0
>
>
> Felix exports an empty system package when the felix "extra" configuration property starts with a semicolon.
> For instance, with the following configuration 
> org.osgi.framework.system.packages.extra=${jre-${java.specification.version}}
> jre-1.5=; \
>  com.sun.accessibility.internal.resources; \
>  com.sun.beans; \
>  ...
> Then, Felix interprets the semicolon (the one after "jre-1.5=") as an empty system package, which is exported to other bundles.
> This may lead to tricky issues, especially for bundles using "DynamicImport-Package: *".
> For instance, the following code returns null, when getting a resource from the bundle archive (and when there is 
> "DynamicImport-Package: *" in the manifest):
> ->
>   InputStream in = getClass().getClassLoader().getResourceAsStream("MyResource.properties");

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.