[jira] [Commented] (MDEP-649) dependency:resolve-plugins lacks includeParents user property

["Dennis Schridde (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MDEP-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17292193#comment-17292193 ] 

Dennis Schridde commented on MDEP-649:
--------------------------------------

[~rfscholte],[~nick.stolwijk]: Indeed changing the default is not a good idea. But that is not necessary: `dependency:get` has `transitive=true`, but `dependency:resolve` has `excludeTransitive=false` by default. So the two use inverse names for the same functionality with the same default behaviour (with the inverse default value, though).

> dependency:resolve-plugins lacks includeParents user property
> -------------------------------------------------------------
>
>                 Key: MDEP-649
>                 URL: https://issues.apache.org/jira/browse/MDEP-649
>             Project: Maven Dependency Plugin
>          Issue Type: New Feature
>          Components: resolve-plugins
>    Affects Versions: 3.1.1
>            Reporter: Dennis Schridde
>            Priority: Major
>
> `dependency:resolve` has an `includeParents` user property [1] which `dependency:resolve-plugins` is lacking [2]. This makes it difficult to generate a complete list of all (JARs and) POMs required to build a project (with dependencies and plugins and their dependencies).
> P.S. `dependency:get` appears to have a similar shortcoming: It can resolve dependencies recursively (`{{transitive}}=true`, enabled by default [3]), but it lacks a `{{includeParents}}` user property.
> [1]: [https://maven.apache.org/plugins/maven-dependency-plugin/resolve-mojo.html#includeParents]
> [2]: [https://maven.apache.org/plugins/maven-dependency-plugin/resolve-plugins-mojo.html]
> [3]: Which BTW is inverse to the disabled-by-default `{{excludeTransitive}}` user property of `dependency:resolve`
>  



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