Despite the package name org.eclipse, these are all parts of Apache Maven. The Eclipse package name is a historical artifact.
On Mon, Apr 8, 2019 at 1:49 AM Michael Lipp <m...@mnl.de> wrote: > > Thanks to everybody who answered. However, I'm utterly confused. > > The references to the examples > (https://github.com/GoogleCloudPlatform/cloud-opensource-java/tree/master/dependencies > and > https://github.com/apache/maven-resolver/tree/master/maven-resolver-demos/maven-resolver-demo-snippets/src/main/java/org/apache/maven/resolver/examples) > effectively all use org.eclipse.aether (e.g. > https://github.com/apache/maven-resolver/blob/master/maven-resolver-demos/maven-resolver-demo-snippets/src/main/java/org/apache/maven/resolver/examples/ResolveArtifact.java > doesn't use a single class from org.apache.maven.*). > > It somehow makes me wonder what the point of the org.apache.maven.* API > is. I was under the impression that it is "the way to go" when you want > to make use of an existing, maven-project-supported library for working > with maven repositories and artifacts. But now I'm left with the > impression that nobody really uses it and I shouldn't care about it and > rather use org.eclipse.aether. Is this correct? > > - Michael > > -- 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
