Avoiding the danger of introducing circular dependencies between different levels and sub-components of Bigtop testing framework, Roman and I have rejected the idea of building multi-module top level Maven project.
Instead, we have a number of loosely coupled sub-projects that depends on each other. The result, while sub-optimal, allows us to treat Bigtop artifacts as first class citizens and use them as dependencies for other projects. The benefit comes with the cost. And most obvious one is a subtle intricacy of the build process.
It has been documented on a number of occasions but the process is still sensitive to a particular order and error prone.
The most pressing issue for me is to have a one-button-click way of building the hole Maven stack at once.