-
Notifications
You must be signed in to change notification settings - Fork 37
Description
You have the closeAndReleaseStagingRepository task (which should probably better be called closeAndReleaseStagingRepositories).
This task is always registered no matter which repositories are configured.
This is good, as then we also get type-safe accessors for the Kotlin DSL for it.
And as typically only Maven Central is configured, this is also a perfect replacement for the closeAndReleaseSonatypeStagingRepository task that does not get accessors generated.
The problem is, that I don't want to do close and release coupled.
I do the closing when doing also other publishing tasks like creating the GitHub publication.
Only after also all other tasks were successful, I want to release the repository.
So I would welcome closeStagingRepositor(y/ies) and releaseStagingRepositor(y/ies) to conveniently wire them using Kotlin DSL.