This is exactly what we do in our multi-project setup, too. And for the same reasons you listed. It works well for me.
I'd be interested to hear, too, what other developers think and experience. Regards, Etienne On 17.10.2010, at 13:50, Dierk König wrote: > Here is a small design question: > why do we need a special handling for testing > in the source sets, tasks, configurations, etc? > > Having played a little with multi-project setup, > it seems to me that a separate test project > that depends on the main project would > just as well do the job without introducing > any special handling. > > IDEs would map this as dependent modules > and would thus provide the same support as > today. > > Some tasks may become easier like excluding > test code from coverage, checkstyle, > and documentation. > > Any opinions on the benefits/downsides of > this? Has someone ever tried this setup? > > cheers > Dierk > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > Etienne Studer Senior Software Developer Canoo Engineering AG Kirschgartenstrasse 5 CH-4051 Basel T +41 61 228 94 44 F +41 61 228 94 49 [email protected] www.canoo.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
