apache / apache/maven-dependency-plugin
[MDEP-649] dependency:resolve-plugins lacks includeParents user property
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Dennis Schridde](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=devurandom)** opened **[MDEP-649](https://issues.apache.org/jira/browse/MDEP-649?redirect=false)** and commented
`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`
---
**Affects:** 3.1.1
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the dependency:resolve-plugins goal and compare its documented user properties with dependency:resolve's includeParents option. Then inspect dependency:get and its transitive and excludeTransitive properties; done means the affected goals provide the requested parent-inclusion behavior consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100