Trac #137: Provide example for report filtering, remove pathid reference from examples.
diff --git a/org.jacoco.doc/docroot/doc/ant.html b/org.jacoco.doc/docroot/doc/ant.html
index 9ac7ebc..d2328de 100644
--- a/org.jacoco.doc/docroot/doc/ant.html
+++ b/org.jacoco.doc/docroot/doc/ant.html
@@ -423,7 +423,7 @@
<span class="nr"> 6</span>
<span class="nr"> 7</span> <structure name="Example Project">
<span class="nr"> 8</span> <classfiles>
-<span class="nr"> 9</span> <fileset dir="bin"/>
+<span class="nr"> 9</span> <fileset dir="classes"/>
<span class="nr"> 10</span> </classfiles>
<span class="nr"> 11</span> <sourcefiles encoding="UTF-8">
<span class="nr"> 12</span> <fileset dir="src"/>
@@ -470,30 +470,44 @@
</ul>
<p>
- The structure can be refined with a hierarchy of <code>group</code> elements.
- This way the coverage report can reflect different modules of a software
- project. For each group element the corresponding class and source files can
- be specified separately. For example, the build script of JaCoCo itself
- contains the following declaration to separate the different bundles in the
- report (see the <a href="../coverage/index.html">resulting report</a>):
+ Note that the <code>classfiles</code> and <code>sourcefiles</code> elements
+ accept any
+ <a href="http://ant.apache.org/manual/Types/resources.html#collection">Ant
+ resource collection</a>. Therefore also filtering the class file set is
+ possible and allows to narrow the scope of the report, for example:
</p>
<pre class="source lang-xml">
-<span class="nr"> 1</span><structure name="JaCoCo">
-<span class="nr"> 2</span> <group name="org.jacoco.core">
+<span class="nr"> 1</span><classfiles>
+<span class="nr"> 2</span> <fileset dir="classes">
+<span class="nr"> 3</span> <include name="org/jacoco/examples/important/**/*.class" />
+<span class="nr"> 4</span> </fileset>
+<span class="nr"> 5</span></classfiles>
+</pre>
+
+<p>
+ The structure can be refined with a hierarchy of <code>group</code> elements.
+ This way the coverage report can reflect different modules of a software
+ project. For each group element the corresponding class and source files can
+ be specified separately. For example:
+</p>
+
+<pre class="source lang-xml">
+<span class="nr"> 1</span><structure name="Example Project">
+<span class="nr"> 2</span> <group name="Server">
<span class="nr"> 3</span> <classfiles>
-<span class="nr"> 4</span> <path refid="bundle-org.jacoco.core"/>
+<span class="nr"> 4</span> <fileset dir="${workspace.dir}/org.jacoco.example.server/classes"/>
<span class="nr"> 5</span> </classfiles>
<span class="nr"> 6</span> <sourcefiles>
-<span class="nr"> 7</span> <fileset dir="${workspace.dir}/org.jacoco.core/src"/>
+<span class="nr"> 7</span> <fileset dir="${workspace.dir}/org.jacoco.example.server/src"/>
<span class="nr"> 8</span> </sourcefiles>
<span class="nr"> 9</span> </group>
-<span class="nr"> 10</span> <group name="org.jacoco.report">
+<span class="nr"> 10</span> <group name="Client">
<span class="nr"> 11</span> <classfiles>
-<span class="nr"> 12</span> <path refid="bundle-org.jacoco.report"/>
+<span class="nr"> 12</span> <fileset dir="${workspace.dir}/org.jacoco.example.client/classes"/>
<span class="nr"> 13</span> </classfiles>
<span class="nr"> 14</span> <sourcefiles>
-<span class="nr"> 15</span> <fileset dir="${workspace.dir}/org.jacoco.report/src"/>
+<span class="nr"> 15</span> <fileset dir="${workspace.dir}/org.jacoco.example.client/src"/>
<span class="nr"> 16</span> </sourcefiles>
<span class="nr"> 17</span> </group>
<span class="nr"> 18</span>