on that precise case ("commons" instead of "org.apache.commons"), it's from
past Maven 1 repository format time.
then such case is not added to Central for years, only projects that existed
at early Maven 1 repository time (like junit, for example or other commons)
have such names: it's up to each of those veteran projects to choose to move
from their old Maven 1 compliant coordinates to full groupId.
If you know such veteran projects that did not move, just share and tell them.
Regards,
Hervé
Le vendredi 14 février 2020, 04:23:15 CET Manfred Moser a écrit :
> This is a left over from bad choices made decades ago. Now Maven Central has
> well documented criteria ... very contrary to nearly all other binary
> repos..
>
>
> https://central.sonatype.org/pages/ossrh-guide.html
>
> https://central.sonatype.org/pages/requirements.html#correct-coordinates
>
> And the videos linked on the site in which I explain more as well.
>
> Manfred
>
> Jonathan Valliere wrote on 2020-02-13 17:06 (GMT -08:00):
> > 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
