refs #4167 - move classes from models to annotations, add swagger-ann… #4195
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…swagger-annotations dependency to swagger-models
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…-models to swagger-annotations, added dependency on swagger-annotations to swagger-models
The other option to fix #4167 is just moving the OpenAPI30 and OpenAPI31 annotations to a package that doesn't begin with
io.swagger.v3.oas.annotationsbut instead is underio.swagger.v3.oas.models, e.g.io.swagger.v3.oas.models.annotations. The question is whether it's more important to reduce transitive dependencies or have consistent packaging for annotations across the core libraries.