Swagger-Core 1.5.7 Released!

This release provides new functionality for lower-level integration with Swagger and resolves compatibility issues in some deployments where @Provider scanning is not configurable.

Upgrade notes:

• Previously, a JacksonJsonProvider class was bundled in the swagger-jaxrs module. This made configuration of the JSON mapper easy and consistent with what is provided for rendering the swagger json/yaml definitions. Because some deployments need a different mapper configuration, this was causing problems and was removed. If you were relying on the JacksonJsonProvider in the io.swagger.jaxrs.json package, please either copy the logic of this file from the 1.5.6 tag or create your own provider!
• Scanning subresources was inconsistent and didn't always follow the expected patter for @Api and @Path parameters. The commit 8921f2f fixes this, but may create issues for those taking advantage of those "bugs". If you are using subresources, please verify that it's behaving how you like after upgrading to 1.5.7.

Notable features

• Removed Jackson Provider (#1604)
• Multiple swagger definitions supported in a single JVM instance (#1600, #1482, #1636)
• Added vendor extensions to Composed Model (#1596)
• Host, port, basePath configurations added to web.xml, BeanConfig
• Bean Validation added for parameters (#1438)
• Subresource scanning has been improved (#1106, #1614, #1617)
• Filtering of unreferenced definitions when configured in SpecFilter (#1557)

Notable bug fixes

• SimpleRef has been exposed in RefResponse (#1616)