Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gradle] Add recommendations to validate task #5183

Merged

Conversation

jimschubert
Copy link
Member

Adds recommendation/validation to the validate task in the gradle plugin.
This fixes #335 although there's no addition to the maven plugin, because none of CLI/Gradle/Maven do custom recommendations or validation in the generate task.

Replaces #5181

PR checklist

  • Read the contribution guidelines.
  • If contributing template-only or documentation-only changes which will change sample output, build the project before.
  • Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
  • File the PR against the correct branch: master, 4.3.x, 5.0.x. Default: master.
  • Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

@auto-labeler
Copy link

auto-labeler bot commented Jan 31, 2020

👍 Thanks for opening this issue!
🏷 I have applied any labels matching special text in your issue.

The team will review the labels and make any necessary changes.

@jimschubert
Copy link
Member Author

AppVeyor seems messed up, as it is targeted via SHA1 rather than branch and caching in a way which was messed up on my older branch. The errors it reports are unrelated to this PR and are successful on master.

Previously, the Gradle plugin was building in CI against
openapi-generator 4.2.0 and Gradle version 4.10.2. At some point, a
contribution was made with an API which is incomatible at 4.10.2 and due
to a release script error which pinned the local-spec version to release
4.2.0, we didn't notice this inconsistency.

This bumps the project to build against Gradle 5.2.1.
@jimschubert jimschubert requested a review from wing328 February 1, 2020 04:55
@jimschubert jimschubert merged commit c8cd255 into OpenAPITools:master Feb 1, 2020
@jimschubert jimschubert deleted the gradle-validate-recommendations branch February 1, 2020 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add validate --recommend option to maven and gradle plugin options.
1 participant