[
https://issues.apache.org/jira/browse/FELIX-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269285#comment-14269285
]
Richard S. Hall commented on FELIX-4757:
----------------------------------------
The suggested approach is more similar to the approach for handling the
auto-install/start properties where start-levels can be specified as part of
the property. I doubt the processing overhead on this would be significant
given the reasonably small size of strings we are talking about and the fact
that it happens only on startup when lots of other stuff is going on anyway.
One other benefit is that if the user wants to override/add an alias in
config.properties, they can do it in a more targeted way. But, in the end, its
your effort so I'll leave it up to you.
> Native Capabilities should allow OS and Processor alias to load from default
> and config properties
> --------------------------------------------------------------------------------------------------
>
> Key: FELIX-4757
> URL: https://issues.apache.org/jira/browse/FELIX-4757
> Project: Felix
> Issue Type: Improvement
> Components: Framework
> Reporter: Bob Paulin
> Assignee: Bob Paulin
> Priority: Minor
> Fix For: framework-4.6.0
>
>
> The initial implementation of the native os and processor aliases had them
> hard coded inside the NativeCodeClause Class. The aliases should be handled
> in a properties file outside the code to allow them to be overridden and make
> them easier to update within the framework.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
