Ownership of established GAVs and assignment of new ones is all managed by Sonatype as part of the onboarding to OSSRH.
>From all I know there is no policy for changes.. its entirely up to the >projects. Maybe Brian or Joel or someone else who is still with Sonatype can chime in. Also.. fyi there is a feature in Maven that allows migration and such but it is barely used. Manfred Jonathan Valliere wrote on 2020-02-13 19:28 (GMT -08:00): > Is there any kind of planned timeline to force compliance against old > projects? > > For example: > > - Force compliance > - Provide symlinks for backwards compatibility for a limited period of > time (1 year) > - Update Maven clients to provide warnings for symlinks during > builds/tests/etc > > > On Thu, Feb 13, 2020 at 10:23 PM Manfred Moser <manf...@simpligility.com> > wrote: > >> 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: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
