There are traces of it in resolver provider: https://github.com/apache/maven/blob/716cc1fe02661897232a7cc3e4c1bb3b3df3b832/maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultArtifactDescriptorReader.java#L316
And AFAIK, it _does_ obeys it... T On Sat, Feb 15, 2020 at 12:03 AM Manfred Moser <manf...@simpligility.com> wrote: > From what I know it is no taken into account by the resolver. > > > Elliotte Rusty Harold wrote on 2020-02-14 14:25 (GMT -08:00): > > > On Fri, Feb 14, 2020 at 5:12 PM Hervé BOUTEMY <herve.bout...@free.fr> > wrote: > >> > >> Le vendredi 14 février 2020, 14:11:07 CET Elliotte Rusty Harold a écrit > : > >> > Changing group IDs of existing projects is a very bad idea. > >> there is relocation strategy: > >> https://maven.apache.org/guides/mini/guide-relocation.html > >> but AFAIK, it is under-tested... > >> > > > > Interesting. How does that affect dependency mediation? That is, if an > > old artifact (pre relocation) and a newer artifact both appear in the > > dependency graph will both be added to the classpath? Or does Maven > > treat them as the same and pick the one it sees first? > > > > > > > > -- > > Elliotte Rusty Harold > > elh...@ibiblio.org > > > > --------------------------------------------------------------------- > > 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 > >
