Howdy, just FTR: Aether project was originally created in org.sonatype.aether package namespace, and was used in Maven 3.0. Later, it moved to Eclipse, and renamed packages to org.eclipse.aether, and was used in Maven 3.1+.
But, the org.sonatype -> org.eclipse package rename caused havoc in plugins (hard breakage) and plugins were either "works with 3.0" or "works with 3.1+", which spun a lot of "workaround" solutions like MAT was (use of reflection to figure is code dealing with o.s or o.e packaged resolver). Finally, the project moved to Apache Maven, but to avoid repetition of such a breakage, it was decided (and Eclipse gave permission for) to continue to use org.eclipse.aether package namespace until change becomes possible. Resolver 1.x was used in the Maven 3.1+ line, and Resolver 2.x is meant for Maven 4 line. According to this: https://gist.github.com/cstamas/b0605a9fad09de4adcbd4444888baa4c Maven 4 still has to support "Maven 3 plugins", and those do contain "direct resolver API usage", hence package change in Maven 4 timeframe is not possible. Package change becomes possible ONLY when Maven internals become cut off from plugins, when Maven API (the new API introduced in Maven 4) becomes the ONLY way to interact with Maven and Resolver from a plugin, and is likely to happen in "Maven 5". HTH Tamas On Mon, Nov 6, 2023 at 3:05 PM Elliotte Rusty Harold <[email protected]> wrote: > Looking at 1.9.16 it seems the maven-resolver-api artifact is > org.eclipse.aether. That's an...interesting...design and a little > surprising. I'm not sure what to think about that yet, but at least > it's not a new issue. So I'll upgrade to +0 for now. > > > On Mon, Nov 6, 2023 at 9:00 AM Elliotte Rusty Harold <[email protected]> > wrote: > > > > On Mon, Nov 6, 2023 at 7:18 AM Konrad Windszus <[email protected]> wrote: > > > > > > The resolver API is only containing classes below org.eclipse.aether > for historical reasons: > https://github.com/apache/maven-resolver/tree/master/maven-resolver-api/src > > > > > > > Is this still necessary? It seems likely to cause dependency conflicts > > and split package issues. > > > > > > -- > > Elliotte Rusty Harold > > [email protected] > > > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
