Add custom publishing target to publish to Maven Central #997
+166 −5
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.
With the sunsetting of OSSRH, the current version of
gradle-maven-publish-plugincan no longer successfully publish usinggradlew publish. The minimum version of the plugin that can publish to Maven Central requires an upgrade to Gradle 8, which is a large upgrade from the current Gradle 6 and will require upgrades to several other plugins as well.In order to unblock the ability to publish, we implement a custom publishing task in this commit that uses the same set of credentials to use a POST command to publish to maven central. This will allow publishing of new upgrades of okbuck while other upgrades are being scoped.
Description: Unblocks the ability to publish while other upgrades are being considered
Related issue(s):