The Maven 4 API can be used without the whole Maven process/environment. See
https://github.com/apache/maven/blob/7f4c24ca179e1603af5215a7b401f7105c04cbc9/impl/maven-impl/src/test/java/org/apache/maven/impl/standalone/TestApiStandalone.java#L42 Of course, there are limitations, but none of those should concern the access to the resolver API, model building, etc... Le mar. 11 févr. 2025 à 12:50, Elliotte Rusty Harold <elh...@ibiblio.org> a écrit : > On Tue, Feb 11, 2025 at 7:20 AM Guillaume Nodet <gno...@apache.org> wrote: > > > > The resolver API should be avoided in the future as it's supposed > > to be hidden by the Maven 4 API. So I'm not sure it's worth it. > > > > I'm not sure how I feel about that. I've certainly written code in the > past that needed to do resolver-y things but was not a Maven plugin > and did not pull in the rest of Maven. I think at the time we used > Aether? It's been a few years. But a resolver that can be used > independently of core Maven would be very helpful for many projects > that are using the repo and artifacts but not building projects with > Maven. > > -- > 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 > > -- ------------------------ Guillaume Nodet
