From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

if I'm going to write a plugin that is going to be published on the portal and this depends on another module, should this module be published on the portal as well, shouldnt?

This is one of the reasons why you should publish your plugin to Maven Central

See also <https://github.com/gradle/plugin-portal-requests/issues/225>

<https://blog.gradle.org/portal-jcenter-impact#upcoming-plugin-portal-changes>
&gt; The Gradle Plugin Portal will continue to return redirects (`303 See Other`) for artifact queries it cannot serve. Starting July 15, 2024, these redirects will be towards <https://repo.maven.apache.org/maven2|Maven Central> instead of JCenter.

if all your dependencies are published in maven central, your plugin will work when published in gradle plugin portal

True but it kinda defeats the purpose of a repository though... If you're publishing some parts of your plugin to Maven Central, might as well distribute all of it.

Or you _could_ shadow everything too I guess.

The nice thing is if you publish everything in Maven Central, it's also available in the plugin portal

Because of that redirection that <@U019L3NM4PK> mentioned

yep. although if you don't publish to GPP directly, you don't show up in <http://plugins.gradle.org|plugins.gradle.org> search

Maven Central has a bunch of other advantages like tracking stats (at least on OSSRH), supporting relocations, more immutability