Allowing multi-project builds with internal deps that have never been built to at least start to build

Maven-Dependency-Tree doesn't seem to resolve from within the reactor. (I thought it did).

This means that while we can fix things so that the build can proceed, we have a small problem with multi-module builds that have never been built that have a dep on an AAR or APK. We won't be able to resolve the deps for these projects, so we won't be able to add the AAR/APK classes to the classpath.

Not sure how to best resolve that. Options:
1) Note that you have to have built your AAR at least once before it can be used as a dep in an APK
2) Making maven-dependency-tree resolve from reactor.
3) Finding alternate for dep resolution that works for both Maven 3 and 3.1 and repo/reactor.