felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-380) provide configuration.properties in the framework.jar by default
Date Tue, 16 Oct 2007 15:37:50 GMT

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

Stuart McCulloch updated FELIX-380:

    Attachment: FELIX_380_20071016.txt

Here's a suggested patch (FELIX_380_20071016.txt) to centralize the JRE package lists.

Basic idea:
 - config.properties holds the primary JRE package lists
 - default.properties uses BND macros to include these lists
 - include config.properties in the BND instructions (to get the package lists)
 - use ${dollar} to protect early expansion of certain properties
 - define <dollar>$</dollar> in the BND instructions

I've tried this with trunk and it appears to work ok

btw, ignore the "target/classes/default.properties" file, as this isn't processed by BND.
it's just been copied across by Maven - look at the one in the actual bundle jar instead

> provide configuration.properties in the framework.jar by default
> ----------------------------------------------------------------
>                 Key: FELIX-380
>                 URL: https://issues.apache.org/jira/browse/FELIX-380
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.0
>            Reporter: Costin Leau
>            Assignee: Richard S. Hall
>         Attachments: FELIX_380_20071016.txt
> Even when using just the framework felix as an embedded library, it is helpful to have
the default configuration.properties (which specifies the packages) loaded automatically and
present in the jar.
> The configuration could be overwritten at startup so clients that want different packages
can do that while clients that do not interact with this aspect can have a resonable default
loaded for them (which is our case = Spring OSGi).
> Thanks.

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

View raw message