You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2016/01/27 12:45:40 UTC
[jira] [Commented] (CXF-6760) extract swagger2 feature in its own
module
[ https://issues.apache.org/jira/browse/CXF-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119103#comment-15119103 ]
Sergey Beryozkin commented on CXF-6760:
---------------------------------------
Hi Romain, it makes sense as it looks like the swagger related code can grow up quite a bit (I'm not even completely rejecting the idea of implementing Swagger spec in Java :-)), though we won't have time to do it for the coming 3.1.5 in the next couple of days, more likely for 3.1.6
> extract swagger2 feature in its own module
> ------------------------------------------
>
> Key: CXF-6760
> URL: https://issues.apache.org/jira/browse/CXF-6760
> Project: CXF
> Issue Type: Bug
> Affects Versions: 3.1.4
> Reporter: Romain Manni-Bucau
>
> the feature is not provided *with*dependencies so if cxf is in the container and swagger the webapp then it leads very easily to issues.
> Having an external module would make it smoother for integrations and doesnt really hurt CXF.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)