On 08.12.2011 Lance Norskog wrote:
> Given all this (especially the third), a separate Maven sub-project makes
> more sense; it should not be part of the default build.

It may just be my personal preference, but I prefer having unit test accompany 
the maven module they test. That also makes checking coverage easier. 
Introducing a separate profile that is only executed on e.g. a nightly Jenkins 
build as suggested by Frank earlier is useful for that.

Isabel

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to