[MDEP-650] dependency:unpack doesn't seem to handle version ranges

**[Andy Lehane](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=alehane)** opened **[MDEP-650](https://issues.apache.org/jira/browse/MDEP-650?redirect=false)** and commented

This call is a reopened version of MDEP-50.

I have a maven-dependency-plugin configuration of:

```java

org.apache.maven.plugins
maven-dependency-plugin


unpack commons-lang example
process-resources

unpack




commons-lang
commons-lang
[0,)
jar
true
${project.build.directory}/test

```

When this is run using maven 3.6.0 and the maven-dependency-plugin version 3.1.1, the following error is produced:

```java
[INFO] --- maven-dependency-plugin:3.1.1:unpack (unpack commons-lang example) @ MavenDependencyPluginTestBed ---
[INFO] Configured Artifact: common-lang:commons-lang:[0,):jar
Downloading from central-proxy: http://internal-repo/repository/central/commons-lang/commons-lang/%5B0,)/commons-lang-%5B0,).pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ---------------------------------------------------------------
```

---

**Affects:** 3.1.1

**Remote Links:**
- [GitHub Pull Request #11
](https://github.com/apache/maven-dependency-plugin/pull/11)
- [GitHub Pull Request #12
](https://github.com/apache/maven-dependency-plugin/pull/12)

2 votes, 3 watchers

Start by reproducing the dependency:unpack configuration with Maven 3.6.0 and maven-dependency-plugin 3.1.1, observing the request generated for version [0,). Review the remote pull requests #11 and #12 for prior work; done means a version range is resolved instead of being used literally in the repository path.

Written by the indexing model from the issue text.