a dependency has a type, but not really a packaging: a packaging is a recipe to build a project that will produce multiple artifacts, each with its own type
see the comparison [1] and default artifact handlers [2] gives you informations about default types. The only misleading field IMHO is that a type does not really define a packaging: there is a typical packaging that produces the type, but anybody could attach an artifact by hand without using the packaging recipe (and if someone produces his artifact with a build tool that is not Maven, the packaging is not used at all) Regards, Hervé [1] https://maven.apache.org/shared/maven-artifact-transfer/comparison.html [2] http://maven.apache.org/ref/current/maven-core/artifact-handlers.html ----- Mail original ----- De: "Elliotte Rusty Harold" <elh...@ibiblio.org> À: "Maven Developers List" <dev@maven.apache.org> Envoyé: Jeudi 20 Septembre 2018 22:05:42 Objet: Packaging from Aether With Eclipse Aether I can read a pom and gather information in the form of import org.eclipse.aether.graph.Dependency and org.eclipse.aether.artifact.Artifact objects. Is there some way from these or related objects I can gather the information about the packaging of the dependency? That is, the type child element of the dependency element in the original pom.xml file? I seem to be able to get the extension of the file, but that's not quite the same thing. -- 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
