Additional task for both publishing and closing staging repository

[matshou]

There should be a single Gradle task that both published and closes staging repository.

For now we have to run the following Gradle command to achieve this:

./gradlew publishToSonatype closeSonatypeStagingRepository

It would be a lot simpler to have an aggregate task that could be called like such:

./gradlew publishToSonatypeAndCloseStagingRepository

[szpak]

Looking at the implementation details publishing is somehow different operation than releasing. It can be done separately or with different configuration. Would you also want to have one for publishToSonatypeAndCloseAndReleaseStagingRepository?

[matshou]

Would you also want to have one for publishToSonatypeAndCloseAndReleaseStagingRepository ?

That would also be useful, perhaps it can be called publishToSonatypeAndReleaseStagingRepository.

[szpak]

That would also be useful, perhaps it can be called publishToSonatypeAndReleaseStagingRepository.

This is somehow inconsistent with other tasks. In the context of preceding publishing the release operation has to be done before the release on, but in general release can be used on its own (e.g. if the new version is published and staging repository is closed and after manual testing that version is being released - in a separate Gradle call, even days after the previous operation).

In the past we had also requests to limit number of tasks, with the argument used that if needed, it is easy to create a small orchestrating tasks (with dependsOn), while removing or hiding task is somehow more complicated.

Personally, I'm not a big fan of adding that task(s), but let's wait for opinions of the other users.

[marcphilipp]

I don't think we need this combined task. The more task combinations we add the more confusing it gets, doesn't it?