Use Maven Central Publisher API #584
Merged
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.
This commit updates the template to use the new publishing task, which makes use of the Publisher API. This API is more reliable than the old one since Maven Central changed their backend.
However, this requires that projects update their root project's build script to use the new "parent" plugin, as seen in this PR.
In other words, publishing will fail if that plugin is not applied.
In addition, this reverts Gradle to 8.14.x, since our builds are NOT ready for Gradle 9 (in particular any project which uses a Kotlin 1.9 plugin will FAIL).
Note for reviewers: I have successfully released Test Resources 2.10.1 using this new process.