[jira] [Resolved] (MDEP-694) Include import-scoped dependency in the output of the dependency plugin goals (e.g. `analyze`, `resolve`, `tree`, `list`, ...)

["Elliotte Rusty Harold (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MDEP-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold resolved MDEP-694.
----------------------------------------
    Resolution: Won't Fix

> Include import-scoped dependency in the output of the dependency plugin goals (e.g. `analyze`, `resolve`, `tree`, `list`, ...)
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MDEP-694
>                 URL: https://issues.apache.org/jira/browse/MDEP-694
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>            Reporter: John Wu
>            Priority: Major
>         Attachments: hello-bom.pom.xml, hello-model.pom.xml
>
>
> * Currently, there is no way to include/show an import-scoped dependency in the output of `dependency:list` (and other similar goals). It is understood that an import-scoped dependency won't result in any binary form artifact (such as jar, war, zip, etc). But it is, by definition, a project dependency. Not listing it in the output prevents tools/scripts from detecting such dependency relationship (without parsing the POM file), thus further messing up the build/manipulation process;
>  * See the attached POM file of `hello-bom` and `hello-model` for examples;
>  * It's acceptable to add an option to control if import-scoped dependency should be included in the output.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)