Trac #143: use colon as separator character in agent parameters

1 files changed, 4 insertions, 4 deletions

diff --git a/org.jacoco.doc/docroot/doc/agent.html b/org.jacoco.doc/docroot/doc/agent.html
index 7d110caa..fad164bb 100644
--- a/org.jacoco.doc/docroot/doc/agent.html
+++ b/org.jacoco.doc/docroot/doc/agent.html
@@ -81,7 +81,7 @@
     <tr>

       <td><code>includes</code></td>

       <td>A list of class names that should be included in execution analysis.

-          The list entries are separated by a vertical bar (<code>|</code>) and

+          The list entries are separated by a colon (<code>:</code>) and

           may use wildcard characters (<code>*</code> and <code>?</code>).

           Except for performance optimization or technical corner cases this

           option is normally not required. 

@@ -91,7 +91,7 @@
     <tr>

       <td><code>excludes</code></td>

       <td>A list of class names that should be excluded from execution analysis.

-          The list entries are separated by a vertical bar (<code>|</code>) and

+          The list entries are separated by a colon (<code>:</code>) and

           may use wildcard characters (<code>*</code> and <code>?</code>).

           Except for performance optimization or technical corner cases this

           option is normally not required. 

@@ -101,8 +101,8 @@
     <tr>

       <td><code>exclclassloader</code></td>

       <td>A list of class loader names that should be excluded from execution

-          analysis. The list entries are separated by a vertical bar

-          (<code>|</code>) and may use wildcard characters (<code>*</code> and

+          analysis. The list entries are separated by a colon

+          (<code>:</code>) and may use wildcard characters (<code>*</code> and

           <code>?</code>). This option might be required in case of special

           frameworks that conflict with JaCoCo code instrumentation, in

           particular class loaders that do not have access to the Java runtime