Re: Maven GroupID authority

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Maven GroupID authority

Elliotte Rusty Harold
FYI, this appears to be a case where Maven does not follow relocations
seamlessly:

https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-923

On Sat, Feb 22, 2020 at 4:33 AM Hervé BOUTEMY <[hidden email]> wrote:

>
> for people interested in working on this relocation topic:
>
> 1. I just updated the relocation guide to add some details gathered from the
> current discussion [1]
>
> 2. I'll be at JChateau unconference [2] mid-march: if people want to join, we
> could probably work on this topic
>
> Regards,
>
> Hervé
>
> [1] https://maven.apache.org/guides/mini/guide-relocation.html
>
> [2] https://www.jchateau.org/
>
> Le jeudi 20 février 2020, 08:54:53 CET Hervé BOUTEMY a écrit :
> > +1
> >
> > probably will start by improving the documentation, because this is really
> > the current intent from what I can understand: a relocation pom only
> > provides relocation info only, no jar, no build info
> >
> > like https://repo.maven.apache.org/maven2/ant/ant/1.7.0/ that points to
> > https://repo.maven.apache.org/maven2/org/apache/ant/ant/1.7.0/
> >
> > AFAIK, there is no modification expected on existing artifacts, just
> > relocation poms to create at old coordinates to point new coordinates = the
> > new canonical coordinates
> >
> >
> > then perhaps the way it is implemented can be improved: one issue I can see
> > (from a pure theoretical point of view, I didn't take time to make extensive
> > tests) is to define when you stop publishing relocation poms at old
> > coordinates, ie. starting with which version?
> > and how to be sure that the relocation is detected when resolving both old
> > coordinates and new coordinates that are both canonical coordinates?
> >
> > for example ant:ant:1.6.5 (= canonical coordinates for this release) and
> > org.apache.ant:ant:1.8.0 (= canonical coordinates for this release), given
> > there is no relocation pom published for ant:ant:1.8.0, only for
> > ant:ant:1.7.0
> >
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 19 février 2020, 16:48:38 CET Jonathan Valliere a écrit :
> > > Maybe we need to rework how this functionality works.  It should be
> > > essentially a symlink with a warning message within the resolver so they
> > > both resolve to the same artifact.
> > >
> > > On Wed, Feb 19, 2020 at 8:58 AM Anders Hammar <[hidden email]> wrote:
> > > > In real practice it doesn't work well though, as someone already brought
> > > > up. It can result in duplication of libraries on the class path (the
> > > > same
> > > > library under different groupId).
> > > >
> > > > /Anders (mobile)
> > > >
> > > > Den ons 19 feb. 2020 14:52Elliotte Rusty Harold <[hidden email]>
> > > >
> > > > skrev:
> > > > > I set up some simple projects and tested this manually. As best I can
> > > > > determine, relocation does work as one would hope, at least in Maven
> > > > > and M2E. (No idea about Gradle or Ivy.)
> > > > >
> > > > > The documentation should probably be rewritten because it assumes you
> > > > > can change published pom.xml files, which isn't true on Maven central.
> > > > >
> > > > > On Mon, Feb 17, 2020 at 3:36 PM Hervé BOUTEMY <[hidden email]>
> > > > >
> > > > > wrote:
> > > > > > you can test with
> > > > > > https://repo.maven.apache.org/maven2/ant/ant/1.7.0/ant-1.7.0.pom
> > > >
> > > > https://repo.maven.apache.org/maven2/javax/xml/jaxrpc/1.1/jaxrpc-1.1.pom
> > > >
> > > >
> > > > https://repo.maven.apache.org/maven2/javax/xml/jaxb-api/1.0.1/jaxb-api-1
> > > > .0
> > > > .1.pom>
> > > >
> > > > > > testing relocation was on my todo list for years, but I never really
> > > >
> > > > test
> > > >
> > > > > > Regards,
> > > > > >
> > > > > > Hervé
> > > > > >
> > > > > > Le dimanche 16 février 2020, 15:18:17 CET Elliotte Rusty Harold a
> > > >
> > > > écrit :
> > > > > > > On Sun, Feb 16, 2020 at 2:35 AM <[hidden email]> wrote:
> > > > > > > > see:
> > > > > > > > -
> > > >
> > > > http://maven.apache.org/ref/3.6.3/maven-model/maven.html#class_relocatio
> > > > n
> > > >
> > > > > > > > - https://maven.apache.org/guides/mini/guide-relocation.html
> > > > > > >
> > > > > > > The guide to relocation seems to assume a lot more access and
> > > > > > > control
> > > > > > > to the repo than is the case with public repositories like Maven
> > > > > > > Central. I'm not sure it's actually possible to follow these steps
> > > > > > > today, though perhaps that could be changed.
> > > > > > >
> > > > > > > I'd still like to see the code in the repo that implements support
> > > >
> > > > for
> > > >
> > > > > > > this or, better yet, a sample project that demonstrates relocation
> > > > > > > is
> > > > > > > possible.
> > > > > > >
> > > > > > > If this does work, I can see a lot of use cases for it, but I'm
> > > > > > > currently working with the assumption it is not.
> > > > > >
> > > > > > --------------------------------------------------------------------
> > > > > > -
> > > > > > To unsubscribe, e-mail: [hidden email]
> > > > > > For additional commands, e-mail: [hidden email]
> > > > >
> > > > > --
> > > > > Elliotte Rusty Harold
> > > > > [hidden email]
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: [hidden email]
> > > > > For additional commands, e-mail: [hidden email]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


--
Elliotte Rusty Harold
[hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]