apache / apache/maven-dependency-plugin
[MDEP-187] dependency:copy fails when invoked from m2e with workspace resolution enabled, or more generally when copying within reactor for phases earlier than package
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Igor Fedorenko](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=igorf)** opened **[MDEP-187](https://issues.apache.org/jira/browse/MDEP-187?redirect=false)** and commented
m2e resolves workspace artifacts to their output folders but dependency:copy expects all artifacts to be files. I will provide trivial patch shortly.
---
**Affects:** 2.1
**Attachments:**
- [MDEP-187.diff](https://issues.apache.org/jira/secure/attachment/12715058/MDEP-187.diff) (_912 bytes_)
- [MDEP-187b.diff](https://issues.apache.org/jira/secure/attachment/12714989/MDEP-187b.diff) (_6.07 kB_)
- [MDEP-187c.diff](https://issues.apache.org/jira/secure/attachment/12715009/MDEP-187c.diff) (_2.45 kB_)
**Issue Links:**
- [MDEP-259](https://issues.apache.org/jira/browse/MDEP-259) copy-dependencies fails with "Error copying artifact from .../target/classes to .../classes"
(_**"is duplicated by"**_)
- [MDEP-291](https://issues.apache.org/jira/browse/MDEP-291) Error when copying within reactor for phases earlier than package
(_**"is duplicated by"**_)
- [MASSEMBLY-411](https://issues.apache.org/jira/browse/MASSEMBLY-411) Error on copy dependencies using Assembler Plugin (m2e Eclipse Plugin Workspace Resolution)
- [MDEP-98](https://issues.apache.org/jira/browse/MDEP-98) dependency:unpack: The source must not be a directory
- [MDEP-194](https://issues.apache.org/jira/browse/MDEP-194) ArchiverException when using maven dependency plugin in multi-module projects
- [MDEP-394](https://issues.apache.org/jira/browse/MDEP-394) unpack behaves differently in multi-module build
**Remote Links:**
- [GitHub Pull Request #31
](https://github.com/apache/maven-plugins/pull/31)
56 votes, 63 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the dependency:copy goal and the attached MDEP-187 diffs, then reproduce the failure with m2e workspace resolution enabled or during a reactor phase before package. Done means dependency:copy handles workspace output directories and reactor artifacts without reporting a copy failure.
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
- 15/100