On 22/03/2016 21:35, Paul Benedict wrote:
Split packages is an important testing feature; less so for production
code. Maven heavily relies on it for unit and integrating testing. Projects
need to be able to build modules, have other modules rely on them, but the
test cases need to "live" in the same packages (but different module) to
access private-package classes.
and just to say that we have options for injecting tests into modules at
both compile time and runtime. These command line options aren't
sometime that many developers will grok but I hope we get to the point
where the tools makes it easy.
-Alan
