[FELIX-3883] [Framework] Move OS and processor aliases to configuration properties

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: framework-4.2.0
• Fix Version/s: framework-4.6.0
• Component/s: Framework
• Assignee: Bob Paulin
• Reporter: Richard S. Hall
• Created: 31/Jan/13 20:15
• Updated: 27/Apr/15 07:03
• Resolved: 09/Jan/15 03:04

Description

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.

Issue Links

• is related to: FELIX-4690 Some bundles containing native code can fail to start on Windows 7+
• relates to: FELIX-4757 Native Capabilities should allow OS and Processor alias to load from default and config properties