[MASSEMBLY-848] Version range dependencies not resolved from the reactor

**[Mark Raynsford](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=io7m)** opened **[MASSEMBLY-848](https://issues.apache.org/jira/browse/MASSEMBLY-848?redirect=false)** and commented

When using modules that have independent version numbers (that is, modules in the same project may have different version numbers), it's commonplace to specify dependencies between modules with version ranges when using semantic versioning.

For some reason, when version ranges are used on dependencies that refer to modules that are part of the project (and therefore should be in the reactor), the assembly plugin ignores them and tries to resolve them from the local repository instead.

The following project reproduces this issue (just "mvn clean package"):

https://github.com/io7m/independent-versioning-20170207

Interestingly, this didn't happen with the same assembly plugin on older Maven versions. Here's a successful build on Travis CI:

https://travis-ci.org/io7m/independent-versioning-20170207

---

**Affects:** 3.0.0

**Attachments:**
- [mvn.log.gz](https://issues.apache.org/jira/secure/attachment/12851618/mvn.log.gz) (_25.32 kB_)

**Remote Links:**
- [GitHub Pull Request #104
](https://github.com/apache/maven-plugins/pull/104)

Start by running `mvn clean package` in the linked independent-versioning-20170207 reproducer and reviewing the attached mvn.log.gz for the failed dependency resolution. Compare the behavior with the older successful Travis CI build and the linked pull request; done means reactor dependencies specified with version ranges resolve from the reactor rather than the local repository.

Written by the indexing model from the issue text.