Created by: jenseng
Refs #3358
Ensure deprecated operations are annotated/documented as such on the
generated methods. Libraries updated:
- [feign]
- [google-api-client]
- [microprofile]
- [okhttp-gson]
- [resttemplate]
- [retrofit]
- [retrofit/play*]
- [webclient]
- [vertx]
Ensure deprecated schemas are annotated/documented as such on the
generated classes/fields. Libraries updated:
- [feign]
- [google-api-client]
- [jersey2]
- [microprofile]
- [native]
- [okhttp-gson]
- [rest-assured]
- [resteasy]
- [resttemplate]
- [retrofit*]
- [webclient]
- [vertx]
Also fix two minor bugs to get the java sample tests working:
- Fix an invalid jackson-datatype-threetenbp version number in vertx/pom.mustache
- Fix a bad return type in webclient/api_test.mustache when uniqueItems=true
Since this commit updates petstore-with-fake-endpoints-models-for-testing.yaml,
several other samples were updated, but it's just new files to reflect the
deprecated schemas, so there should be no consequential differences.
Relevant bits of the spec:
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.2.md#user-content-operationdeprecated
- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.2.md#user-content-schemadeprecated
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master,5.1.x,6.0.x -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request. CC @bbdouglas @sreeshas @jfiala @lukoyanov @cbornet @jeff9finger @karismann @Zomzog @lwlee2608 @nmuesch