Having just read through the "Guide to relocation", and having never consciously encountered this in the wild (I'm not a big name in this community, but I have used Maven extensively for many years), this seems to be a solution to direct users to a new groupId when they are upgrading to a new version. It might not be a solution at all to help with dependency resolution (when two conflicting versions of essentially the same artifacts are brought on the classpath because they no longer have matching coordinates). Perhaps someone could elaborate who understands the relocation mechanism better?
Sander Verhagen [ san...@sanderverhagen.net<mailto:san...@sanderverhagen.net> ] On 15/02/2020 23.35, herve.bout...@free.fr<mailto:herve.bout...@free.fr> wrote: see: - http://maven.apache.org/ref/3.6.3/maven-model/maven.html#class_relocation - https://maven.apache.org/guides/mini/guide-relocation.html Everything is there. I confess I never tried it myself, but there are POMs in central using it. ----- Mail original ----- De: "Elliotte Rusty Harold" <elh...@ibiblio.org><mailto:elh...@ibiblio.org> ?: "Maven Developers List" <dev@maven.apache.org><mailto:dev@maven.apache.org> Envoy?: Samedi 15 F?vrier 2020 19:35:09 Objet: Re: Maven GroupID authority On Sat, Feb 15, 2020 at 1:29 PM Jonathan Valliere <jon.valli...@emoten.com><mailto:jon.valli...@emoten.com> wrote: If Central indicated a redirect/reallocation then there would never be the duplicate classpath problem because Maven would resolve it internally. The redirect then warns the user of the redirect and to update the pom. I really don't think Maven works like that, but feel free to point me to the code in Github that proves me wrong.
