This almost works. However, it is also necessary to be able to define the source fileset.
For example:
<target name="with.clover">
<property name="clover.enabled" value="true" />
<fileset id="clover.sources" dir="${basedir}">
<include name="*/src/java/" />
<include name="*/test/java/" />
<exclude name="gensrc/" />
</fileset>
<clover-setup enabled="${clover.enabled}" initstring="${clover.db}">
<fileset refid="clover.sources" />
...
When the clover-check targets are calculated they seem to be including our generated classes, found under gensrc/. We do not wish to consider the generated classes for coverage, and they are already properly omitted from the coverage reports.
Can clover-check limit itself to just the fileset already configured in clover-setup? If not can it accept a fileset itself, just like clover-report?
Medium
This almost works. However, it is also necessary to be able to define the source fileset.
For example:
<target name="with.clover">
<property name="clover.enabled" value="true" />
<fileset id="clover.sources" dir="${basedir}">
<include name="*/src/java/" />
<include name="*/test/java/" />
<exclude name="gensrc/" />
</fileset>
<clover-setup enabled="${clover.enabled}" initstring="${clover.db}">
<fileset refid="clover.sources" />
...
When the clover-check targets are calculated they seem to be including our generated classes, found under gensrc/. We do not wish to consider the generated classes for coverage, and they are already properly omitted from the coverage reports.
Can clover-check limit itself to just the fileset already configured in clover-setup? If not can it accept a fileset itself, just like clover-report?