[
https://issues.apache.org/jira/browse/FELIX-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530467
]
Richard S. Hall commented on FELIX-380:
---------------------------------------
After thinking about this with Costin, I agree it could be possible to do
something reasonable. Effectively, we could embed a stripped down
config.properties file in our launcher (i.e., main.jar), but have main.jar
still search for "conf/config.properties". If it finds the file, it uses the
file contents as the configuration properties, otherwise it uses the embedded
config.properties file.
Does that seem like a reasonable approach?
If so, what should be in the embedded config.properties file? Just the
framework exported packages? Or framework exported and JRE packages? I assume
no "auto" properties.
> 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
>
> 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.
