Skip to content
GitLab

[gradle plugin] Release 4.0.1 fixes

Merged Jim Schubert requested to merge gradle-plugin-release-fixes into master

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\. If contributing template-only or documentation-only changes which will change sample output, be sure to build the project first.
  • Filed the PR against the correct branch: master, 4.1.x, 5.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Covers some issues we had with reworking the gradle plugin publishing in 4.0.1 release:

  • Found that the plugin's version wasn't being updated in scripting (addressed in #3047)
  • The publishPluginMavenPublicationToNexusRepository task only delivers a subset of files required by Sonatype in order for release (needed publishMavenJavaPublicationToNexusRepository)
  • username, password, and stagingProfileId weren't configured properly for the nexusPublishing task

This will need to be updated after #3047 is merged to change the version in gradle.properties to 4.0.2-SNAPSHOT.