Thanks Gareth.
It sounds as if Maven doesn't have the ability to determine and resolve
inter-project dependencies when packaging a child.
If a sub-module-A has a dependency on a module-B and module-B isn't
package, Maven will not package module-B prior to packaging
sub-module-A. Again, this is
This is exactly correct.
If you want to build and package *only* your submodule, then Maven
needs to have the other dependencies already installed in your local
repo... it won't go find them, build, and use them even if they share
a parent.
This will work if executed from the top/parent pom.
