We know from M2 experience and the number of "profiles" in the
integration branch that a top-down, build-everything approach does
not work.
We also know from practical experience that people struggle building
modules.
I believe there is a middle ground that supports both approaches;
* have a flat module structure that allows any module to be built on
its own
using dependencies from the mvn repos
* have particular assemblies that pull modules together into whatever
bundles
people want. The assemblies can use released modules from mvn,
snapshot
modules from mvn, a copy of any revision of that module, or can track
trunk using svn externals
An example of this is the assembly I used for the tag for the TSSS
demo code which uses a combination of released artifacts and known
revisions.
This gives module developers their own space to work in, and allows
people consuming those modules to choose how stable the code they
want to use is (from released through to head).
Hopefully this will provide a middle ground we are all comfortable with.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
