Francesco Tumanischvili

Atm this is not possible; support for such a scenario is planned, but probably it won't make it for next release.

see also #2694 which reports the same behaviour

What you are trying to achieve is something not supported by OAS 2.0 (swagger) or 3.0 and JSON Schema Draft 4: in these versions a schema declaring a `$ref` has...

we have 3.1 in our short term roadmap, please check [this comment in swagger-parser](https://github.com/swagger-api/swagger-parser/issues/1535#issuecomment-936707841) for details

#4129 introduces support for OAS 3.1 representation (swagger-models), serialization and deserialization. code first resolution of OAS 3.1 spec in `ModelResolver` and JAXRS Reader (both via conversion and additional annotations resolution)...

As you're mentioning an URL I assume you are referring to `externalValue` field of `@ExampleObject` annotation, mapping to [corresponding spec element](https://github.com/OAI/OpenAPI-Specification/blob/3.0.1/versions/3.0.1.md#exampleObject) which allows to specify an external URL providing the...

@gcatanese swagger-core oas 3.1 effort has been merged into master branch (and is part of latest release). This means that a ref with `description` and/or `summary` siblings (for non JSON...

Please try with 2.0.6 version, providing a different [`contextId` param](https://github.com/swagger-api/swagger-core/tree/master/modules/swagger-maven-plugin#parameters) in each execution e.g. ```xml openapi-1 openapi-1 ... openapi-2 openapi-2 ... ```

Thanks!! merged #4105 and #4106 On the side `ObjectMapper` used by resolver can be customized by providing a `objectMapperProcessorClass` in [configuration](https://github.com/swagger-api/swagger-core/wiki/Swagger-2.X---Integration-and-Configuration#configuration-properties)

Thanks a lot! merged #4286 which includes #4221