johnzon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Rathgeb <maggu2...@gmail.com>
Subject Re: [VOTE] Johnzon 1.2.0
Date Fri, 13 Sep 2019 15:28:31 GMT
Hi,

> > I’d like to call a VOTE on the Apache Johnzon 1.2. This is the Jakarta>
> > JSON-B and Jakarta JSON-P compatible version.


You state that this release is compatible for Jakarta.
I already posted today a problem I run into using 1.1.12 and I assume
it should be solved by this release if it targets the Jakarta
artifact.
But I don't think it is solved.

The JSON-B artifact of Johnzon 1.2 contains this manifest entry:

Require-Capability: osgi.extender;filter:="(osgi.extender=osgi.service
 loader.registrar)",osgi.contract;osgi.contract=JavaJAXRS;filter:="(&(
 osgi.contract=JavaJAXRS)(version=2.1.0))",osgi.contract;osgi.contract
 =JavaAnnotation;filter:="(&(osgi.contract=JavaAnnotation)(version=1.3
 .0))",osgi.contract;osgi.contract=JavaCDI;filter:="(&(osgi.contract=J
 avaCDI)(version=2.0.0))",osgi.contract;osgi.contract=JavaJSONB;filter
 :="(&(osgi.contract=JavaJSONB)(version=1.0.0))",osgi.contract;osgi.co
 ntract=JavaJSONP;filter:="(&(osgi.contract=JavaJSONP)(version=1.1.0))
 ",osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.8))"

So, it uses the OSGi contracts in its manifest.

The Jakarta CDI API version 2.0.2 does NOT provide the OSGi contracts.
It seems OSGi contracts are not part of the Jakarta JARs.

Mime
View raw message