@x2on What do you gain by publishing Gradle plugins to other repositories? The canonical (and currently one supported) way is to publish them to gradle.org. If you adhere to this, publishing should simply work.
I’d really like to understand your process here, so I am wondering is if there are concrete reasons for us to support a workflow that involves publishing Gradle plugins to other repositories than our own. If there are, we will have to consider them.
I understand from previous discussions that we might support a workflow that involves staging to e.g. Sonatype, but those artifacts would be private and not published per se.