apache / apache/maven-dependency-plugin
[MDEP-881] dependencyManagement to dependencies
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Delany](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=delany)** opened **[MDEP-881](https://issues.apache.org/jira/browse/MDEP-881?redirect=false)** and commented
Before releasing a BOM type artefact, e.g. in https://reflectoring.io/maven-bom/
I'd like to confirm that the artefacts I've specified are actually available. Currently there's no way to do this without making a redundant \ section in the project with an entry for every dep in depMng and running the resolve goal.
Could there be a new property includeManagement on the resolve goal? Or a separate resolveManaged goal?
Alternatively, a goal that generates a dependency for every managed dependency which subsequent goals can work off, e.g.
```java
mvn dependency:depend oga-maven-plugin:check ossindex:audit
```
---
**Affects:** 3.6.0
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the dependency:resolve goal and how it handles dependencyManagement. Compare the proposed includeManagement, resolveManaged, and generated-dependency approaches, then verify that managed dependencies can be resolved or checked without a redundant dependencies section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100