Fedora sub-modules cannot be build/verified/tested before their module dependencies are not installed in the local Maven repository. This exposes resolving dependencies and individual module testing to dependency errors (e.g. building against invalid Kernel API).
A "clean machine" that has never seen Fedora before should be able to execute `mvn validate` and `mvn dependency:resolve` successful. When purging all Fedora related artifacts from the local Maven repository (or starting on a new machine) this is not possible anymore (see attached build report).
Using `mvn install` every time changes have been made to separate modules not only takes too long, but also introduces the problem of "out-dated snaphots" in the local repository if dependencies have not been installed in the right order previously. It further corrupts IDE integration (as I noticed using IntelliJ) and seems to raise a problem for individual module testing.
Running `mvn -am -pl fcrepo-kernel-modeshape validate` the build fails as soon as <bannedDependencies/> is added to the enforcer plugin configuration, even without any exclusions configured.