[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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1
• Component/s: copy, copy-dependencies
• Assignee: Unassigned
• Reporter: Igor Fedorenko
• Created: 12/Nov/08 16:26
• Updated: 09/Apr/20 13:37

Description

m2e resolves workspace artifacts to their output folders but dependency:copy expects all artifacts to be files. I will provide trivial patch shortly.

Issue Links

• is duplicated by: MDEP-259 copy-dependencies fails with "Error copying artifact from .../target/classes to .../classes"
• is duplicated by: MDEP-291 Error when copying within reactor for phases earlier than package
• is related to: MDEP-394 unpack behaves differently in multi-module build
• relates to: MASSEMBLY-411 Error on copy dependencies using Assembler Plugin (m2e Eclipse Plugin Workspace Resolution)
• relates to: MDEP-98 dependency:unpack: The source must not be a directory
• relates to: MDEP-194 ArchiverException when using maven dependency plugin in multi-module projects
• links to: GitHub Pull Request #31