Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Currently often the dependency's type is being set to the extension and the resolution is lenient, i.e. if there is no artifact handler defining the value given in dependency->type resolution transparently uses the type as extension.
That can potentially lead to two issues:
1. Resolution might fail with surprising error messages like
Could not resolve dependencies for project ....: The following artifacts could not be resolved: <gav>: Could not transfer artifact <groupId>:<artifactId>:<unknown-type>:<version> from/to ...
This is an issue for all types not defined by Maven Core itself, e.g. for https://jackrabbit.apache.org/filevault-package-maven-plugin/index.html which registers an artifact handler for type content-package with extension zip.
2. The information addedToClasspath, includesDependencies and classifier from the artifact handler is not evaluated
Compare with https://maven.apache.org/repositories/artifacts.html#but-where-do-i-set-artifact-extension
Attachments
Issue Links
- links to