Sergey Beryozkin commented on CXF-7045:

Hi Andriy, 
I see what your concern is, why would CXF worry about facilitating installing 
Jackson's only concern, as far as OSGI is concerned, is to have each of those 
5+ jars OSGI-friendly. 
But even so, we haven't had any specific Jackson support till now.

I guess all the features that we ship with CXF enable something atomically. So 
if we have a swagger2 feature that does not actually  enable Swagger unless a 
user manually pre-installs Jackson then I'd say the feature is incomplete.

But Swagger2 OSGI feature actually has an indirect support for Jackson right 
now. So we can make it work with Option3. But we can also make it work by 
introducing cxf-jackson, and as you said have the existing swagger2feature 
depend on it - it will be mostly equivalent to what we right now but the extra 
benefit that CXF users can use cxf-jackson on its own...

Thanks, Sergey

> Update sample description_swagger2_osgi README.txt
> --------------------------------------------------
>                 Key: CXF-7045
>                 URL: https://issues.apache.org/jira/browse/CXF-7045
>             Project: CXF
>          Issue Type: Bug
>          Components: Samples
>            Reporter: John Poth
>            Assignee: Freeman Fang
>            Priority: Minor
>             Fix For: 3.2.0, 3.1.8
> Update jackson version. Currently getting the error:
> {code}
> Caused by: org.osgi.framework.BundleException: Unable to resolve 
> org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0): 
> missing requirement [org.apache.cxf.samples.jax_rs_description_swagger2_osgi 
> [146](R 146.0)] osgi.wiring.package; 
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))
>  Unresolved requirements: 
> [[org.apache.cxf.samples.jax_rs_description_swagger2_osgi [146](R 146.0)] 
> osgi.wiring.package; 
> (&(osgi.wiring.package=com.fasterxml.jackson.jaxrs.json)(version>=2.6.0)(!(version>=3.0.0)))]
> {code}

This message was sent by Atlassian JIRA

Reply via email to