This issue is to discuss the state of one of our upstream dependency Swagger-Parser.
Original project: https://github.com/swagger-api/swagger-parser/pulls
Our fork: https://github.com/OpenAPITools/swagger-parser/pulls
In our fork, we have started to do some fixes on the 2.0-OpenAPITools branch.
Personally I would prefer to have the issues fixed in the original project. Otherwise this means that we will have to publish a release of OpenAPITools/swagger-parser under new maven coordinates (using our groupId)
I would prefer not fragmenting the swagger-parser project.
I am using other tools like openapi-diff and I would like all project to use the same version of swagger-parser. Otherwise this means that we will have a dependency management hell.
I propose that we still open issue and file PRs in the original swagger-parser project. I know there is little reaction at the moment, but it would be better on the long term.
We can also add all the PRs we have created on the original project to our 2.0-OpenAPITools
If they do not integrate our fixes we will be forced to create a release of org.openapitools:swagger-parser based on the 2.0-OpenAPITools. But I hope this will not be necessary.
This issue is to discuss the state of one of our upstream dependency
Swagger-Parser.Original project: https://github.com/swagger-api/swagger-parser/pulls
Our fork: https://github.com/OpenAPITools/swagger-parser/pulls
In our fork, we have started to do some fixes on the 2.0-OpenAPITools branch.
Personally I would prefer to have the issues fixed in the original project. Otherwise this means that we will have to publish a release of
OpenAPITools/swagger-parserunder new maven coordinates (using our groupId)I would prefer not fragmenting the
swagger-parserproject.I am using other tools like openapi-diff and I would like all project to use the same version of
swagger-parser. Otherwise this means that we will have a dependency management hell.I propose that we still open issue and file PRs in the original
swagger-parserproject. I know there is little reaction at the moment, but it would be better on the long term.We can also add all the PRs we have created on the original project to our
2.0-OpenAPIToolsIf they do not integrate our fixes we will be forced to create a release of
org.openapitools:swagger-parserbased on the2.0-OpenAPITools. But I hope this will not be necessary.