[MDEP-950] 'copy dependency' feature doesn't allow for packaging only the dependencies required during the compile phase.

**[Calvin Kirs](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=kirs)** opened **[MDEP-950](https://issues.apache.org/jira/browse/MDEP-950?redirect=false)** and commented

I've been using the Maven dependency plugin to package my binary application, but ensuring it includes only the compile-phase dependencies has been a challenge. I've reviewed the documentation[1], but it doesn't meet my needs. I'm struggling with the context behind this design decision, and why it was initially set up this way. Of course, if there are alternative approaches that require additional development, I'm willing to contribute.

https://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html#includescope

---
No further details from [MDEP-950](https://issues.apache.org/jira/browse/MDEP-950?redirect=false)

Start with the Maven dependency plugin copy-dependencies documentation, especially the includescope section linked in the issue, and inspect how the current copy-dependencies goal defines dependency scopes. Clarify the expected compile-phase behavior and its relationship to the existing design before identifying implementation and test entry points; done means the requested packaging behavior is supported and documented.

Written by the indexing model from the issue text.