[
https://issues.apache.org/jira/browse/FELIX-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved FELIX-5742.
-------------------------------
Resolution: Fixed
Done in r1814500.
I add a felix.detect.jpms property that maps to "jpms" if we are on >= java9
(i.e., jpms). From there, we now use the property substitution to pick the
current java9 definitions.
Granted, this is not really correct as we don't get the right osgi.ee set, the
package version will still be 0.0.0.9, and in general, there might be new
packages with new usage-constraints etc. However, we at least will be able to
start-up on > java9.
> Provide java9 system bundle exports for jpms jre
> ------------------------------------------------
>
> Key: FELIX-5742
> URL: https://issues.apache.org/jira/browse/FELIX-5742
> Project: Felix
> Issue Type: Sub-task
> Components: Framework
> Affects Versions: framework-5.6.8
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Fix For: framework-5.6.10
>
>
> Until now, the framework needed to be aware of the java version it was
> running on to determine the system bundle exports (and capabilities). In
> other words, a new java version required a new framework release with updated
> default properties.
> As it currently looks as if java versions will be released much more often in
> the future we should at a minimum make it so that we fall back to the current
> java9 definitions when on jpms.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
