apache / apache/maven-dependency-plugin
[MDEP-597] Copy goal resolves Parent POM unnecessarily
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Peter Wippermann](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peter.wippermann)** opened **[MDEP-597](https://issues.apache.org/jira/browse/MDEP-597?redirect=false)** and commented
I'm running `dependency:copy` via the CLI to download a .jar artifact. This leads to a long list of downloads during the plugin's execution since the artifact's POM, its Parent POM and all imported BOMs are resolved.
Is this really necessary? You might argue that downloading the artifact's POM is absolutely needed, but I don't see the point of resolving the parent (and the rest) as well.
---
**Affects:** 3.0.2
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the dependency:copy CLI execution and trace how the artifact POM, its parent POM, and imported BOMs are resolved. Confirm the expected behavior for downloading a .jar and verify that unnecessary parent and BOM resolution no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100