A question about publishing to Maven Central. I have a library on GitHub and a publication setup via GitHub Actions. There are 5 jobs that publish different targets in parallel. The issue is that it creates multiple staging repositories in Nexus Repository Manager. So I have some questions: 1. Is it a problem at all? Maybe I should just close/release all the created repositories? 2. How people usually approach publications of MPP libs to Maven Central, specially if there are targets that must be built on different hosts (macOS/Windows/etc)

This might help https://kotlinlang.slack.com/archives/C0BJ0GTE2/p1612455781100500?thread_ts=1612372634.063700&cid=C0BJ0GTE2

Thanks @Big Chungus, this article is indeed useful, but it does not cover this particular topic, unless I'm missing something.

Have a read through that entire slack thread. Might be something directly useful for you there.

The easier way is just configure as normal and close the repos (one per machine), but you can take a look to @mbonnin GitHub, he has an action to just use one repo

The sample: https://github.com/nexus-actions/nexus-actions-demo

Yeah, in these cases, I just drop them because they usually are corrupted

This plugin, right ? https://github.com/gradle-nexus/publish-plugin/

Yeah

Thanks, I will check!

That plugin doesn't fix that problem at this moment. It fixes a problem where you get a random number of repos. For example, having only one machine, you should only get one repo, but sometimes, you get like 3 or 4 repos with the artifacts mixed randomly. That plugin ensures you get 1 repo per machine.

That makes sense, thanks. I will try the GitHub action trick.