You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2019/01/10 09:31:00 UTC
[jira] [Resolved] (KARAF-6084) Startup bundles do not resolve
correctly when compiled with Java 11 during assembly
[ https://issues.apache.org/jira/browse/KARAF-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved KARAF-6084.
---------------------------------
Resolution: Fixed
> Startup bundles do not resolve correctly when compiled with Java 11 during assembly
> -----------------------------------------------------------------------------------
>
> Key: KARAF-6084
> URL: https://issues.apache.org/jira/browse/KARAF-6084
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.2.2
> Reporter: Martin Krüger
> Assignee: Freeman Fang
> Priority: Major
> Fix For: 4.2.3
>
> Attachments: 0001-KARAF-6084-Add-Java-11-and-11-to-the-list-of-support.patch
>
>
> The problem is that we have a fragment for the logger which needs to be loaded in the startup phase. We compile the bundles with Java 11 which results in a {noformat}Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))"{noformat} manifest entry. We during build we get an error that a bundle requirement is not met.
> We then discovered that the karaf-maven-plugin uses "1.8" as default value for the javase option. Changing that to "11" results in a compile error because this version is not supported.
> Therefore I suggest to add Java 10 and Java 11 to enum org.apache.karaf.profile.assembly.Builder.JavaVersion. That enables support for this Java version also.
> In my local tests this solved the compile issue when setting the javase option to 11.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)