Konrad Windszus created MNG-8097: ------------------------------------ Summary: Validate that each dependency->type is a type registered in an artifact handler Key: MNG-8097 URL: https://issues.apache.org/jira/browse/MNG-8097 Project: Maven Issue Type: New Feature Reporter: Konrad Windszus
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 {code} 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 ... {code} 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}} and {{includesDependencies}} from the artifact handler is not evaluated -- This message was sent by Atlassian Jira (v8.20.10#820010)