We run /all/ tests prior to /every/ delivery. Our project contains many
modules, some of which are low-level components, others represent
top-level servers. It does not matter what you have changed, before
committing you must update, rebuild, and run all tests.
But with a run-target being based on a /module's/ classpath it would
seem now that we would have to know the roots of the module forest,
define a testall target for each, then make sure to run each of them
individually as part of a delivery.
Do I understand this correctly? Do we need to create a psuedo module
that simply contains all other modules (and of course their named
libraries :( just to use for the testall target?
If so, it would be nice if the project as whole could be one of the
selections for the classpath/jdk of a run-target.