You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2020/12/11 21:00:00 UTC
[jira] [Resolved] (FELIX-6222) Support for os.name Capability is
missing for Windows Server 2019
[ https://issues.apache.org/jira/browse/FELIX-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls resolved FELIX-6222.
-------------------------------
Resolution: Fixed
Thanks. Fixed in trunk.
> Support for os.name Capability is missing for Windows Server 2019
> -----------------------------------------------------------------
>
> Key: FELIX-6222
> URL: https://issues.apache.org/jira/browse/FELIX-6222
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-6.0.3
> Environment: OS: Windows Server 2019
> JDK: OpenJDK8u232 (hotspot)
> Felix: 5.6.10
> Reporter: Paul Stanley
> Assignee: Karl Pauls
> Priority: Major
> Fix For: framework-6.0.4
>
>
> Bundles with native libraries fail to run on Windows Server 2019
> As of OpenJDK-11.0.3, oracle-JDK8u222 and OpenJDK8u212 the windows server operating system is now reported correctly as "Windows Server 2019". However the NativeLibraryClause class in the felix-framework doesn't understand this value and as such it reverts the os.name capability to simply win32.
> Please can you extend the NativeLibraryClause to cope with the new operation system name. like you have done for all the other Windows variants.
> This has been seen as a problem on version 5.6.10 of the felix.framework (as shipped with glassfish 5.1), but is also present in the current code base.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)