Skip to content
GitLab

[Java-client] Add maven-compiler-plugin in pom.xml and enable linter checks by default

Merged Administrator requested to merge github/fork/CiscoM31/java-client-mvn into master

Created by: sebastien-rosset

  1. Add maven-compiler-plugin plugin to the pom.mustache template. This makes it possible to configure arguments for the compilation phase.
  2. Set -Xlint:all argument by default in the pom.xml. This is used to identify linter warnings. These warnings should be fixed.
  3. Fix warnings identified by linter in step 2.
  4. Configure pom.xml to fork the java compiler and specify memory parameters. This helps to compile the generated code when the input OAS document is a big file.

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.