Marcin Zajączkowski

It's already mentioned in the [migration guide](https://github.com/gradle-nexus/publish-plugin/wiki/Migration-from-gradle_nexus_staging-plugin---nexus_publish-plugin-duo#configuration---more-customizations), but I agree it would be good to have it documented also in README.

Good point. I merged it without thinking about that aspect :-/. I will think if it is easier to rollback it or release a new version :-).

@ThomasJejkal It's not official, but you can take a look at the minimal project used in the e2e tests ran on CI: https://github.com/gradle-nexus/nexus-publish-e2e-minimal/blob/master/build.gradle

@ThomasJejkal Feel free to propose a README improvement to make it more obvious about the publishing plugin.

> @szpak Do you want to take another look? No, thank you. You know much better all the tricks & tips with the Gradle API and Kotlin :-). If the...

Unfortunately, it is not supported at the moment. Your case is similar to support for the mono repo projects (#84) and the Android projects (#75). While your extra requirement to...

Good idea! It would make it easier to spot (among others) missing artifact signatures (which results in the error on closing which has to be examined using the Nexus UI).

From the time I was writing GNSP I remember that the API was poorly documented and I needed to analyze the official Maven plugin calls to get know about some...

> I think we could add a stagingRepositoryId property to the InitializeNexusStagingRepository task and write it to a file. I don't see this as must-have for the initial release, though....

401 means Unauthorized. Probably there was no response body from the server (as you should see something like in https://github.com/gradle-nexus/publish-plugin/issues/55). Are you sure you set your credentials (preferably your token-username...