You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Bob Paulin (JIRA)" <ji...@apache.org> on 2015/01/09 04:05:34 UTC

[jira] [Resolved] (FELIX-3883) [Framework] Move OS and processor aliases to configuration properties

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

Bob Paulin resolved FELIX-3883.
-------------------------------
    Resolution: Fixed

> [Framework] Move OS and processor aliases to configuration properties
> ---------------------------------------------------------------------
>
>                 Key: FELIX-3883
>                 URL: https://issues.apache.org/jira/browse/FELIX-3883
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: framework-4.2.0
>            Reporter: Richard S. Hall
>            Assignee: Bob Paulin
>             Fix For: framework-4.6.0
>
>
> Currently, we hard code our OS and processor aliases for matching native code libraries. This is bad since it requires us to edit source code to add aliases. It would be better if we moved these to configuration properties, something like this:
>     felix.native.os.[normalname] = alias1, alias2, etc.
>     felix.native.arch.[normalname] = alias1, alias2, etc.
> More concretely:
>     felix.native.os.win32 = Windows 8, Windows 7, Windows Vista
>     felix.native.arch.x86 = i386, i486, i586
> We could then use the properties to define as many "normal names" as we want and associate all their known aliases, so at run time all names could be normalized.
> We can include a default set of normal names and aliases in default.properties, but allow people to override any of them (or add new normal names/aliases) in config.properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)