#79 Allow cobertura-report to take dirset for source dirs

[Anonymous]

I would like the ability to use a dirset as the source dir input for the cobertura report task like this:

<cobertura:report datafile="${cobertura.datafile}" destdir="${reports.dir}/cobertura">
<dirset dir="${modules.dir}" includes="**/src/main/java"/>
</cobertura:report>

We have a multi-module project (each with similar dir structures). I don't want to have to list each module's src dir in separate filesets as currently required. For example, currently, I have to do this:

<cobertura:report datafile="${cobertura.datafile}" destdir="${reports.dir}/cobertura">
<fileset dir="${modules.dir}/moduleA/src/main/java" includes="**/*.java"/>
<fileset dir="${modules.dir}/moduleB/src/main/java" includes="**/*.java"/>
<fileset dir="${modules.dir}/moduleC/src/main/java" includes="**/*.java"/>
<fileset dir="${modules.dir}/moduleD/src/main/java" includes="**/*.java"/>
<fileset dir="${modules.dir}/moduleE/src/main/java" includes="**/*.java"/>
<fileset dir="${modules.dir}/moduleF/src/main/java" includes="**/*.java"/>
<fileset dir="${modules.dir}/moduleG/src/main/java" includes="**/*.java"/>
</cobertura:report>

We don't really statically maintain a module list anywhere in our build (we use ivy's buildlist task to construct the module list dynamically). I don't really want to introduce this static list just for generating coverage data.

[Vladimir Tsukur]

Our team would also benefit from this feature since specifying a list of hardcoded filesets is a obviously a bad configuration solution.