As mentioned there are two issues here, nested vs flat structure and the
One can easily go without the other.
I personally like the flat hierarchy.
Simply using the artifact id to create a hierarchy or a reactor pom is
only working in same cases. I fear we have some "wrong" artifact ids to
be useful for this.
Now, for the use case at hand, why can't we simply add profiles to the
reactor pom. By default all projects are in the reactor, but if you
specify a profile like "htl" only htl related modules are triggered.
Nice, easy, extensible and requires zero changes
Radu Cotescu wrote
Adobe Research Switzerland