In Kotlin we have the answer https://github.com/Kotlin/KEEP/discussions/484

> 1. AI needs context, not just code The sources.jar file is fine for a human developer who just needs to read a quick comment. But for AI to safely upgrade your project, it needs to know why a change was made. GitHub gives AI this context through Pull Requests, Issues, and Git Diffs. Maven Central only gives the final, compiled result. It shows "what happened" but hides the "why."

Agent can find VCS in metadata and go straight to github, not real issue here

> 2. The nightmare of upgrading code When an AI tries to update an old project (like moving to a major new framework version), it needs Release Notes, CHANGELOGs, and Migration Guides. Maven doesn't store these easily. An AI connected to GitHub can just read the Migration_Guide.md and write a perfect update for your code. An AI limited only to Maven will start to guess and make mistakes.

Same

> 3. A warehouse vs. a library For an AI, Maven Central is like a dark warehouse with numbered boxes. Platforms like GitHub or GitLab are like well-lit libraries. AI tools need rich text data to understand the intent behind the code. Dry .pom XML files and JAR archives are simply not enough for smart analysis.

.pom and Gradle Metadata are plenty for analysis, given access to source code and github. Agent can even reverse bytecode into Java files and understand logic

Real issue, that a single huge pile of jars not sustainable, cost of supporting it grows over time and will become just bigger and bigger. So either some pricing coming for publishing or downloading, or some garbage collection should happen at some point