Sergey Beryozkin commented on CXF-7045:

Hi Andriy, I'm actually thinking it will become easier for the users.

Lets take it step by step.
- Users need Jackson (without even worrying about Swagger) - they have to do 
*5* install commands, see
So having Jackson feature in its own is good IMHO - only one install command.
- Now users install Swagger 2 feature and all works.

Having Swagger2 feature forcing the install of Jackson is OK as long as this 
Jackson will not interfere with other installed Jacksons.
So if we 2 swagger features, one for a case where Jackson is already installed 
and one for a case where it has not been installed, then I can only see it 
becoming simpler.

Where is the complexity coming from in your opinion, lets take some concrete 
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