Gradle maven-publish creates multiple repositories

[Florian Schmaus]

Hey,

After multiple years of successfully deploying to OSS sonatype, I am currently unable to deploy a new version.

After "gradle publish" I find multiple staging repositories created, which I can not close, since every repository has different issues because the artifacts are scattered across them.

This appears to be an old open and re-appearing issue (OSSRH-38347, OSSRH-19485). I have commented with more details on

https://issues.sonatype.org/browse/OSSRH-38347?focusedCommentId=932540&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-932540

Not sure why I am suddenly affected by this.

Is there anything I can do to fix this?

- Florian

[Marcin Zajączkowski]

Hi. Yes, it can be done using gradle-nexus-staging-plugin together with
nexus-publish-plugin. See this blog post:
https://solidsoft.wordpress.com/2019/02/22/reliable-releasing-to-maven-central-from-travis-using-gradle-2019-edition/

Btw, in the predicable future you should be able to use just one plugin
(a mix of the aforementioned) -
https://github.com/gradle-nexus/publish-plugin . However, there is no
stable version released yet.

Marcin

--
https://blog.solidsoft.pl/ - Working code is not enough