I'd prefer to make a clear distinction between the build tool and the shared repositories like Maven Central. Here the problem should be solved by the latter.
And it is: https://central.sonatype.org/pages/choosing-your-coordinates.html Unlike module names, you must claim a groupId before pushing it to Maven Central. Central contains some bad picked groupId from the early days, but now that most are used to the value of a groupId, I don't see a real risk here. Robert On 14-2-2020 02:07:03, Jonathan Valliere <jon.valli...@emoten.com> wrote: I have been growing concerned about the process of allowing the creation of GroupIDs, within the Maven Central repository, which do not adhere to the naming guidelines. i.e. the GroupID must belong to a unique domain name controlled by the project owner. Even within the Apache family, there is no consistent naming enforcement. The project I belong to, org.apache.mina adheres to the conventions but many others do not. Apache Commons for example uses a different GroupID for almost every sub-project within its scope. Many of them simply starting with the word "commons" instead of "org.apache.commons". Does the PMC have any ideas on how to combat this? Cheers, Jon
