This message was deleted.

probably https://github.com/gradle/gradle/blob/master/subprojects/plugin-development/src/main/java/org/gradle/plugin/devel/plugins/MavenPluginPublishPlugin.java

No, I’m talking about the com.gradle.plugin-publish plugin that communicates with the plugin portal. I’m starting to think it’s closed source, given the com in its id…

Yes, it’s closed source.

Thanks Benedikt! I wanted to look at it mostly to understand why it exists 😄 AFAIU it hides away all the complexity of communicating with the plugin portal. But I’m curious about why it is complex in the first place, what makes it need more than a

credentials

block.

It’s indeed closed source, but mostly due to legacy/accidental reasons. We do want to open-source it, but unfortunately it’s pretty low on our priority list… it does hide all the complexity of communicating with the portal, but it also does a lot of wiring together (forcing source and javadoc artifacts, signing, …) and checking (versions, vulnerabilities, …); even the communication part is not as simple as it seems, because it’s the plugin that uploads artefacts directly to S3, not the portal; we have simplified it a lot lately, but it’s still an ugly beast… I hope we can make OS soon, it would definitely improve it in the long term