Marek Parfianowicz added a comment - 10/Feb/2014 8:50 AM Update: we already have a <profiles> tag, but it does not have so many settings as shown in a sample above.

Marek Parfianowicz added a comment - 24/Jul/2012 7:22 AM This task will add profiles internally only. However, we could add later support for in in Ant/Maven. The existing clover-setup task: <clover-setup initstring-and-other-attributes> <distributedCoverage/> <files/> <fileset/> <methodcontext/> <statementcontext/> <testsources> <testclass> <testmethod/> </testclass> </testsources> </clover-setup> would be changed to: <clover-setup initstring-and-other-attributes> <!-- One or more profiles can be defined, each with mandatory name --> <profile name="name-of-profile" initstring-and-other-attributes> <distributedCoverage/> <files/> <fileset/> <methodcontext/> <statementcontext/> <testsources> <testclass> <testmethod/> </testclass> </testsources> </profile> <!-- Left for backward compatibility --> <distributedCoverage/> <files/> <fileset/> <methodcontext/> <statementcontext/> <testsources> <testclass> <testmethod/> </testclass> </testsources> </clover-setup> we'd have the implicit profile named "default" into which all attributes from <clover-setup> as well as tags directly below <clover-setup> would be kept. we can have multiple profiles defined at runtime user can define sth like "-Dclover.profile=profile-name" we could also define an "empty" profile, which would use NullRecorder, thus would write no data to disk Major benefit I see is that code is instrumented once and ready to be executed on multiple environments