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
