Skip to content

Conversation

@maggu2810
Copy link

@maggu2810 maggu2810 commented Apr 30, 2016

No description provided.

@maggu2810
Copy link
Author

Handle the jersey2-jaxrs jar similar to the other ones that already brings OSGi support.

@webron
Copy link
Contributor

webron commented May 2, 2016

@elakito - can you have a look at this please?

@elakito
Copy link
Contributor

elakito commented May 3, 2016

@webron i'll look at it today.

@elakito
Copy link
Contributor

elakito commented May 3, 2016

@webron it looks okay.

One remark that I can make is that the existing two jersey components swagger-jersey-jaxrs and swagger-jersey2-jaxrs are not inherently osgi friendly as they contain the same public packages io.swagger.jersey classes. But assuming only this jersey2 one is becoming an osgi bundle and the other one is not, there will be no conflict.

@maggu2810
Copy link
Author

Hi @webron, @elakito do you see any change to get this merged in front of the next release?

@webron
Copy link
Contributor

webron commented Aug 11, 2016

@maggu2810 - can you rebase?

@maggu2810
Copy link
Author

done

@frantuma frantuma merged commit 0c46e6f into swagger-api:master Aug 12, 2016
@fehguy fehguy modified the milestone: 1.5.10 Dec 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants