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 2017/04/26 13:15:04 UTC

[jira] [Resolved] (CXF-7347) Support Swagger UI 3

     [ https://issues.apache.org/jira/browse/CXF-7347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved CXF-7347.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.1.12
                   3.2.0

> Support Swagger UI 3
> --------------------
>
>                 Key: CXF-7347
>                 URL: https://issues.apache.org/jira/browse/CXF-7347
>             Project: CXF
>          Issue Type: New Feature
>            Reporter: Peter van den Broek
>            Assignee: Sergey Beryozkin
>             Fix For: 3.2.0, 3.1.12
>
>         Attachments: swagger3.png, swagger-ui-basepath-127001.PNG, swagger-ui-basepath-localhost.PNG
>
>
> Swagger UI 3.0.0 was released on 18 March 2017 and brings a full rewrite of the UI from the ground up.
> In this version, they've changed the directory structure to being flat with only a couple of files left.
> This means the CSS and JS files are now located in the root of the folder and most files have been merged or removed.
> Swagger2Feature contains an internal SwaggerUIResourceFilter that checks for files in these (no longer existing) subfolders, but does not find the new location of (for example) css files.
> The pattern it uses is:
> {code}
> .*[.]js|/css/.*|/images/.*|/lib/.*|.*ico|/fonts/.*
> {code}
> This no longer works, since it doesn't allow for files (other than JS and ICO) to be in the root folder.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)