You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Raymond Augé (JIRA)" <ji...@apache.org> on 2018/10/22 03:31:00 UTC
[jira] [Commented] (FELIX-5879) Maven-bundle-plugin generates wrong
osgi.ee requirement on JDK 10
[ https://issues.apache.org/jira/browse/FELIX-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658511#comment-16658511 ]
Raymond Augé commented on FELIX-5879:
-------------------------------------
Can you verify this with release 4.1.0? By moving to bnd 4.1.0 which added support for up to Java 11, this should be addressed.
> Maven-bundle-plugin generates wrong osgi.ee requirement on JDK 10
> -----------------------------------------------------------------
>
> Key: FELIX-5879
> URL: https://issues.apache.org/jira/browse/FELIX-5879
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-3.5.0
> Reporter: Gjøran Voldengen
> Priority: Major
>
> When building with JDK 10, maven-bundle-plugin (3.5.1) generates the following manifest attribute:
> {{Require-Capability: osgi.ee;filter:="(osgi.ee=UNKNOWN)"}}
> See [this post on Stackoverflow|https://stackoverflow.com/questions/51138244/maven-bundle-plugin-osgi-ee-unknown] for details. According to the answer from BJ Hargrave, I tried adding an explicit dependency to bndlib 4.0 in the plugin declaration in pom.xml, and got the correct attribute in the manifest:
> {{Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=10.0))"}}
> It would be great if you could release a version of the plugin with {{bndlib}} upgraded to version 4, in order to support JDK 10 without pom.xml hacks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)