Remove trailing whitespaces in HTML, CSS and JS files

29 files changed, 155 insertions, 155 deletions

diff --git a/org.jacoco.build/licenses/googlecodeprettify-20100721.html b/org.jacoco.build/licenses/googlecodeprettify-20100721.html
index 441452aa..11a8a1d3 100644
--- a/org.jacoco.build/licenses/googlecodeprettify-20100721.html
+++ b/org.jacoco.build/licenses/googlecodeprettify-20100721.html
@@ -2,7 +2,7 @@
 
 <p>
   <a href="https://github.com/google/code-prettify">Google Code Prettify 2010/07/21</a>
-  is subject to the terms and conditions of the following license: 
+  is subject to the terms and conditions of the following license:
 </p>
 
 <pre>
diff --git a/org.jacoco.doc/docroot/doc/agent.html b/org.jacoco.doc/docroot/doc/agent.html
index 05eb992d..719a843a 100644
--- a/org.jacoco.doc/docroot/doc/agent.html
+++ b/org.jacoco.doc/docroot/doc/agent.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Java Agent</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Java Agent</h1>
 
@@ -51,7 +51,7 @@
 <p>
   The agent <code>jacocoagent.jar</code> is part of the JaCoCo distribution and
   includes all required dependencies. A Java agent can be activated with the
-  following JVM option: 
+  following JVM option:
 </p>
 
 <pre>
@@ -59,7 +59,7 @@
 </pre>
 
 <p>
-  The JaCoCo agent accepts the following options: 
+  The JaCoCo agent accepts the following options:
 </p>
 
 <table class="coverage">
@@ -83,14 +83,14 @@
           <code>false</code>, an existing execution data file will be replaced.
       </td>
       <td><code>true</code></td>
-    </tr>    
+    </tr>
     <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 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. 
+          option is normally not required.
       </td>
       <td><code>*</code> (all classes)</td>
     </tr>
@@ -114,7 +114,7 @@
           <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
-          classes. 
+          classes.
       </td>
       <td><code>sun.reflect.DelegatingClassLoader</code></td>
     </tr>
@@ -122,7 +122,7 @@
       <td><code>inclbootstrapclasses</code></td>
       <td>Specifies whether also classes from the bootstrap classloader should
           be instrumented. Use this feature with caution, it needs heavy
-          includes/excludes tuning. 
+          includes/excludes tuning.
       </td>
       <td><code>false</code></td>
     </tr>
@@ -130,7 +130,7 @@
       <td><code>inclnolocationclasses</code></td>
       <td>Specifies whether also classes without a source location should be
           instrumented. Normally such classes are generated at runtime e.g. by
-          mocking frameworks and are therefore excluded by default. 
+          mocking frameworks and are therefore excluded by default.
       </td>
       <td><code>false</code></td>
     </tr>
@@ -140,7 +140,7 @@
           this parameter a random identifier is created by the agent.
       </td>
       <td><i>auto-generated</i></td>
-    </tr>  
+    </tr>
     <tr>
       <td><code>dumponexit</code></td>
       <td>If set to <code>true</code> coverage data will be written on VM
@@ -165,7 +165,7 @@
               attribute. Execution data is written to this TCP connection.</li>
           <li><code>none</code>: Do not produce any output.</li>
         </ul>
-        Please see the security considerations below. 
+        Please see the security considerations below.
       </td>
       <td><code>file</code></td>
     </tr>
@@ -203,7 +203,7 @@
       <td>If set to <code>true</code> the agent exposes
           <a href="./api/org/jacoco/agent/rt/IAgent.html">functionality</a> via
           JMX under the name <code>org.jacoco:type=Runtime</code>. Please see
-          the security considerations below. 
+          the security considerations below.
       </td>
       <td><code>false</code></td>
     </tr>
@@ -218,7 +218,7 @@
   authentication mechanism. If you run JaCoCo on production systems make sure
   that no untrusted sources have access to the TCP server port, or JaCoCo TCP
   clients only connect to trusted targets. Otherwise internal information of the
-  application might be revealed or DOS attacks are possible. 
+  application might be revealed or DOS attacks are possible.
 </p>
 
 </div>
diff --git a/org.jacoco.doc/docroot/doc/ant.html b/org.jacoco.doc/docroot/doc/ant.html
index 8b60d514..f0ddfd58 100644
--- a/org.jacoco.doc/docroot/doc/ant.html
+++ b/org.jacoco.doc/docroot/doc/ant.html
@@ -16,7 +16,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Ant Tasks</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Ant Tasks</h1>
 
@@ -28,16 +28,16 @@
   <a href="#agent"><code>agent</code></a>,
   <a href="#dump"><code>dump</code></a> and
   <a href="#merge"><code>merge</code></a>. Reports in different formats are
-  created with the <a href="#report"><code>report</code></a> task. For 
+  created with the <a href="#report"><code>report</code></a> task. For
   <a href="offline.html">offline instrumentation</a> the task
   <a href="#instrument"><code>instrument</code></a> can be used to prepare class
-  files.  
+  files.
 </p>
 
 <p class="hint">
   If you want to have line number information included in the coverage reports
   or you want source code highlighting the class files of the test target must
-  be compiled with debug information. 
+  be compiled with debug information.
 </p>
 
 <h2>Example</h2>
@@ -63,10 +63,10 @@
   <li>Java 1.5 or higher (for both, the Ant runner and the test executor).</li>
 </ul>
 
-   
+
 <p>All tasks are defined in <code>jacocoant.jar</code> (which is part of the
   distribution) and can be included in your Ant scripts with the usual
-  <code>taskdef</code> declaration:   
+  <code>taskdef</code> declaration:
 </p>
 
 <pre class="source lang-xml linenums">
@@ -75,9 +75,9 @@
     &lt;taskdef uri="antlib:org.jacoco.ant" resource="org/jacoco/ant/antlib.xml"&gt;
         &lt;classpath path="<i>path_to_jacoco</i>/lib/jacocoant.jar"/&gt;
     &lt;/taskdef&gt;
-    
+
     ...
-    
+
 &lt;/project&gt;
 </pre>
 
@@ -102,7 +102,7 @@
   The standard Ant tasks to launch Java programs are <code>java</code>, <code>junit</code> and
   <code>testng</code>. To add code coverage recording to these tasks they can
   simply be wrapped with the <code>coverage</code> task as shown in the
-  following examples:  
+  following examples:
 </p>
 
 <pre class="source lang-xml linenums">
@@ -128,7 +128,7 @@
 <p>
   Resulting coverage information is collected during execution and written
   to a file when the process terminates. Note the <code>fork</code> attribute
-  above in the wrapped <code>java</code> task. 
+  above in the wrapped <code>java</code> task.
 </p>
 
 <p class="hint">
@@ -145,7 +145,7 @@
 
 <p>
   The coverage task must wrap exactly one task. While it typically works without
-  any configuration, the behavior can be adjusted with some optional attributes: 
+  any configuration, the behavior can be adjusted with some optional attributes:
 </p>
 
 <table class="coverage">
@@ -174,14 +174,14 @@
           <code>false</code>, an existing execution data file will be replaced.
       </td>
       <td><code>true</code></td>
-    </tr>    
+    </tr>
     <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 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. 
+          option is normally not required.
       </td>
       <td><code>*</code> (all classes)</td>
     </tr>
@@ -204,7 +204,7 @@
           <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
-          classes. 
+          classes.
       </td>
       <td><code>sun.reflect.DelegatingClassLoader</code></td>
     </tr>
@@ -212,7 +212,7 @@
       <td><code>inclbootstrapclasses</code></td>
       <td>Specifies whether also classes from the bootstrap classloader should
           be instrumented. Use this feature with caution, it needs heavy
-          includes/excludes tuning. 
+          includes/excludes tuning.
       </td>
       <td><code>false</code></td>
     </tr>
@@ -220,7 +220,7 @@
       <td><code>inclnolocationclasses</code></td>
       <td>Specifies whether also classes without a source location should be
           instrumented. Normally such classes are generated at runtime e.g. by
-          mocking frameworks and are therefore excluded by default. 
+          mocking frameworks and are therefore excluded by default.
       </td>
       <td><code>false</code></td>
     </tr>
@@ -230,7 +230,7 @@
           this parameter a random identifier is created by the agent.
       </td>
       <td><i>auto-generated</i></td>
-    </tr>  
+    </tr>
     <tr>
       <td><code>dumponexit</code></td>
       <td>If set to <code>true</code> coverage data will be written on VM
@@ -367,7 +367,7 @@
 </p>
 
 <p>
-  The <code>dump</code> task has the following attributes: 
+  The <code>dump</code> task has the following attributes:
 </p>
 
 <table class="coverage">
@@ -428,7 +428,7 @@
 
 <p>
   This task can be used to merge the execution data from multiple test runs
-  into a single data store. 
+  into a single data store.
 </p>
 
 <pre class="source lang-xml linenums">
@@ -439,7 +439,7 @@
 
 <p>
   The task definition can contain any number of resource collection types and
-  has the following mandatory attribute: 
+  has the following mandatory attribute:
 </p>
 
 <table class="coverage">
@@ -465,16 +465,16 @@
 <p>
   Finally different reports can be created with the <code>report</code> task.
   A report task declaration consists of different sections, two specify the
-  input data, additional ones specify the output formats:  
+  input data, additional ones specify the output formats:
 </p>
 
 <pre class="source lang-xml linenums">
 &lt;jacoco:report&gt;
-			
+
     &lt;executiondata&gt;
         &lt;file file="jacoco.exec"/&gt;
     &lt;/executiondata&gt;
-			
+
     &lt;structure name="Example Project"&gt;
         &lt;classfiles&gt;
             &lt;fileset dir="classes"/&gt;
@@ -483,9 +483,9 @@
             &lt;fileset dir="src"/&gt;
         &lt;/sourcefiles&gt;
     &lt;/structure&gt;
-			
+
     &lt;html destdir="report"/&gt;
-			
+
 &lt;/jacoco:report&gt;
 </pre>
 
@@ -558,7 +558,7 @@
   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: 
+  possible and allows to narrow the scope of the report, for example:
 </p>
 
 <pre class="source lang-xml linenums">
@@ -580,7 +580,7 @@
   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: 
+  be specified separately. For example:
 </p>
 
 <pre class="source lang-xml linenums">
@@ -601,9 +601,9 @@
             &lt;fileset dir="${workspace.dir}/org.jacoco.example.client/src"/&gt;
         &lt;/sourcefiles&gt;
     &lt;/group&gt;
-    
+
     ...
-    
+
 &lt;/structure&gt;
 </pre>
 
@@ -680,7 +680,7 @@
 <h3>Element <code>xml</code></h3>
 
 <p>
-  Create a single-file report in XML format. 
+  Create a single-file report in XML format.
 </p>
 
 <table class="coverage">
@@ -708,7 +708,7 @@
 <h3>Element <code>csv</code></h3>
 
 <p>
-  Create single-file report in CSV format. 
+  Create single-file report in CSV format.
 </p>
 
 <table class="coverage">
@@ -899,7 +899,7 @@
 
 <p>
   The task definition can contain any number of resource collection types and
-  has the following mandatory attribute: 
+  has the following mandatory attribute:
 </p>
 
 <table class="coverage">
@@ -918,7 +918,7 @@
     </tr>
     <tr>
       <td><code>removesignatures</code></td>
-      <td>If set to <code>true</code> all signature related information is 
+      <td>If set to <code>true</code> all signature related information is
           stripped from JARs. This is typically necessary as instrumentation
           breaks the signatures of the original class files.</td>
       <td><code>true</code></td>
diff --git a/org.jacoco.doc/docroot/doc/api.html b/org.jacoco.doc/docroot/doc/api.html
index f618c92d..77ce8a95 100644
--- a/org.jacoco.doc/docroot/doc/api.html
+++ b/org.jacoco.doc/docroot/doc/api.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">API Usage Examples</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>API Usage Examples</h1>
 
@@ -42,18 +42,18 @@
       <td><a class="el_source" href="examples/java/CoreTutorial.java">CoreTutorial.java</a></td>
       <td>This tutorial-like example instruments, executes and analyzes a single
           target class. Finally line coverage information is printed to the
-          console. 
+          console.
       </td>
     </tr>
     <tr>
       <td><a class="el_source" href="examples/java/ClassInfo.java">ClassInfo.java</a></td>
       <td>This example writes JaCoCo specific information for given Java class
-          files. 
+          files.
       </td>
     </tr>
     <tr>
       <td><a class="el_source" href="examples/java/ExecDump.java">ExecDump.java</a></td>
-      <td>Utility to dump the content of execution data files in readable form. 
+      <td>Utility to dump the content of execution data files in readable form.
       </td>
     </tr>
     <tr>
diff --git a/org.jacoco.doc/docroot/doc/build.html b/org.jacoco.doc/docroot/doc/build.html
index 9270ace3..3170e622 100644
--- a/org.jacoco.doc/docroot/doc/build.html
+++ b/org.jacoco.doc/docroot/doc/build.html
@@ -34,7 +34,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Build</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Build</h1>
 
diff --git a/org.jacoco.doc/docroot/doc/changes.html b/org.jacoco.doc/docroot/doc/changes.html
index ac3e8615..23de32b4 100644
--- a/org.jacoco.doc/docroot/doc/changes.html
+++ b/org.jacoco.doc/docroot/doc/changes.html
@@ -280,7 +280,7 @@
   <li>JaCoCo now comes with a simple command line interface
       (GitHub <a href="https://github.com/jacoco/jacoco/issues/525">#525</a>).</li>
   <li>Limit configuration of Maven <code>check</code> goal and Ant
-      <code>check</code> element now also supports percentage values 
+      <code>check</code> element now also supports percentage values
       (GitHub <a href="https://github.com/jacoco/jacoco/issues/534">#534</a>).</li>
   <li>Manifests of JAR files now have <code>Automatic-Module-Name</code> for Java 9
       (GitHub <a href="https://github.com/jacoco/jacoco/issues/565">#565</a>).</li>
@@ -496,7 +496,7 @@
 <h3>API Changes</h3>
 <ul>
   <li>In case of incompatible execution data formats read from another JaCoCo
-  version <code>ExecutionDataReader.read()</code> now throws a 
+  version <code>ExecutionDataReader.read()</code> now throws a
   <code>IncompatibleExecDataVersionException</code>.</li>
 </ul>
 
@@ -628,7 +628,7 @@
       includes removal of the specific skip condition for packages e.g. POMs and
       instead checks existence of <tt>target/classes</tt> in appropriate goals
       (GitHub <a href="https://github.com/jacoco/jacoco/issues/171">#171</a>).</li>
-  <li>GitHub #44: (Regression) Agent Mojo should set empty property, if execution was skipped 
+  <li>GitHub #44: (Regression) Agent Mojo should set empty property, if execution was skipped
       (GitHub <a href="https://github.com/jacoco/jacoco/issues/192">#192</a>).</li>
 </ul>
 
@@ -954,7 +954,7 @@
       complexity (Trac #129).</li>
   <li>XML and CSV report includes new counter type <code>COMPLEXITY</code>
       (Trac #129).</li>
-  <li>New method <code>getTabWidth()</code> in callback interface 
+  <li>New method <code>getTabWidth()</code> in callback interface
       <code>ISourceFileLocator</code> instead of
       <code>HTMLReportFormatter.setTabWidth()</code> which has been removed.
       (Trac #152).</li>
@@ -1049,7 +1049,7 @@
 
 <h3>Fixed Bugs</h3>
 <ul>
-  <li>Better error message when multiple JaCoCo agents are specified 
+  <li>Better error message when multiple JaCoCo agents are specified
       (Track #103).</li>
   <li>Fixed potential NPE at shutdown when running agent in
       <code>tcpserver</code> mode (Track #117).</li>
@@ -1082,7 +1082,7 @@
   <li>Additional and modified methods in <code>IRuntime</code> to produce
       session information (Trac #88).</li>
   <li>Coverage element type <code>SESSION</code> removed (Trac #95).</li>
-  <li>Removed several internal APIs from package 
+  <li>Removed several internal APIs from package
       <code>org.jacoco.core.instr</code> used for class instrumentation.</li>
   <li>Renamed class <code>org.jacoco.report.csv.CsvFormatter</code> to
       <code>CSVFormatter</code> (upper case) for consistency with other
diff --git a/org.jacoco.doc/docroot/doc/classids.html b/org.jacoco.doc/docroot/doc/classids.html
index 2db8469c..6086327b 100644
--- a/org.jacoco.doc/docroot/doc/classids.html
+++ b/org.jacoco.doc/docroot/doc/classids.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Class Ids</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Class Ids</h1>
 
diff --git a/org.jacoco.doc/docroot/doc/conventions.html b/org.jacoco.doc/docroot/doc/conventions.html
index 5fc11a55..e449e283 100644
--- a/org.jacoco.doc/docroot/doc/conventions.html
+++ b/org.jacoco.doc/docroot/doc/conventions.html
@@ -14,13 +14,13 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Development Conventions</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Development Conventions</h1>
 
 <p>
   Efficient team work that produces high-quality software requires a common set
-  of rules.  
+  of rules.
 </p>
 
 <h2>Consistent Source Tree</h2>
@@ -40,7 +40,7 @@
   Documentation is part of the product. Whenever you implement a new feature or
   change existing behavior make sure to update all corresponding JavaDoc as well
   as other documentation with the same change set. The product should always be
-  in a consistent state. For every change the following items should be checked:  
+  in a consistent state. For every change the following items should be checked:
 </p>
 
 <ul>
@@ -57,12 +57,12 @@
 <p>
   The primary focus of the JaCoCo project is to provide a code coverage library.
   Integrators may want to embed JaCoCo in different tools and environments with
-  very different usage scenarios. Therefore following aspects should be considered:    
+  very different usage scenarios. Therefore following aspects should be considered:
 </p>
 
 <p>
   <b>Documentation:</b> All APIs should be properly documented on different
-  levels of granularity: 
+  levels of granularity:
 </p>
 
 <ul>
@@ -107,7 +107,7 @@
 <h2>Keep an Eye on License Issues</h2>
 
 <p>
-  All code included with JaCoCo must conform to the EPL license. 
+  All code included with JaCoCo must conform to the EPL license.
 </p>
 
 <ul>
@@ -115,7 +115,7 @@
     Every committer and contributor must agree that all code will be published
     under EPL. He or she must be the original author and must have the
     permission to contribute code to JaCoCo, for example if such a permission
-    is required by the employer. 
+    is required by the employer.
   </li>
   <li>
     Every third party content must be enlisted in the corresponding
@@ -131,7 +131,7 @@
     <a href="http://www.eclipse.org/legal/copyrightandlicensenotice.php">EPL
     license notice</a>. The initial contributor should be listed. In case of
     significant changes or additions additional contributors should also
-    be listed. 
+    be listed.
   </li>
 </ul>
 
diff --git a/org.jacoco.doc/docroot/doc/counters.html b/org.jacoco.doc/docroot/doc/counters.html
index 768fb64a..cc77cd71 100644
--- a/org.jacoco.doc/docroot/doc/counters.html
+++ b/org.jacoco.doc/docroot/doc/counters.html
@@ -14,14 +14,14 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Coverage Counters</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Coverage Counters</h1>
 
 <p>
   JaCoCo uses a set of different counters to calculate coverage metrics. All
   these counters are derived from information contained in Java class files
-  which basically are Java byte code instructions and debug information 
+  which basically are Java byte code instructions and debug information
   optionally embedded in class files. This approach allows efficient on-the-fly
   instrumentation and analysis of applications even when no source code is
   available. In most cases the collected information can be mapped back to
@@ -30,7 +30,7 @@
   information to calculate line level coverage and provide source highlighting.
   Not all Java language constructs can be directly compiled to corresponding
   byte code. In such cases the Java compiler creates so called <i>synthetic</i>
-  code which sometimes results in unexpected code coverage results. 
+  code which sometimes results in unexpected code coverage results.
 </p>
 
 <h2>Instructions (C0 Coverage)</h2>
@@ -82,7 +82,7 @@
 
 <p>
   The formal definition of the cyclomatic complexity v(G) is based on the
-  representation of a method's control flow graph as a directed graph:  
+  representation of a method's control flow graph as a directed graph:
 </p>
 
 <blockquote>
@@ -123,7 +123,7 @@
 <p>
   Due to the fact that a single line typically compiles to multiple byte code
   instructions the source code highlighting shows three different status for
-  each line containing source code: 
+  each line containing source code:
 </p>
 
 <ul>
@@ -164,7 +164,7 @@
   initializers such interfaces are also considered as executable classes.
 </p>
 
-</div> 
+</div>
 <div class="footer">
   <span class="right"><a href="${jacoco.home.url}">JaCoCo</a> ${qualified.bundle.version}</span>
   <a href="license.html">Copyright</a> &copy; ${copyright.years} Mountainminds GmbH &amp; Co. KG and Contributors
diff --git a/org.jacoco.doc/docroot/doc/empty.html b/org.jacoco.doc/docroot/doc/empty.html
index 45bb7760..fbad8caf 100644
--- a/org.jacoco.doc/docroot/doc/empty.html
+++ b/org.jacoco.doc/docroot/doc/empty.html
@@ -13,7 +13,7 @@
   <a href="../index.html" class="el_report">JaCoCo</a> &gt;
   <span class="el_source">Title</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Title</h1>
 
diff --git a/org.jacoco.doc/docroot/doc/environment.html b/org.jacoco.doc/docroot/doc/environment.html
index 2de5c3d6..0f37734d 100644
--- a/org.jacoco.doc/docroot/doc/environment.html
+++ b/org.jacoco.doc/docroot/doc/environment.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Development Environment</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Development Environment</h1>
 
@@ -48,7 +48,7 @@
   Eclipse projects that can be imported in a Eclipse workspace.
 </p>
 
-<p>  
+<p>
   Project specific Eclipse settings only exist for the following projects. All
   other projects and test projects link to these settings:
 </p>
diff --git a/org.jacoco.doc/docroot/doc/faq.html b/org.jacoco.doc/docroot/doc/faq.html
index bd7f9af3..f4e8b53c 100644
--- a/org.jacoco.doc/docroot/doc/faq.html
+++ b/org.jacoco.doc/docroot/doc/faq.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">FAQ</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>FAQ</h1>
 
@@ -29,7 +29,7 @@
   guarantee free capacity, we do not commit to particular release dates.
   Typically, you can expect a couple of releases every year.
 </p>
-<p>  
+<p>
   In the <a href="changes.html">change log</a>, you can see all features
   that have been been implemented in master branch and will be available
   with the next release. And in the meantime you can test latest build of
@@ -166,7 +166,7 @@
   If you use <a href="offline.html">offline instrumentation</a> the instrumented
   classes get a direct dependency on the JaCoCo runtime. Therefore
   <code>jacocoagent.jar</code> of the same JaCoCo version must be on the
-  classpath and accessible from by the instrumented classes. 
+  classpath and accessible from by the instrumented classes.
 </p>
 
 <h3>Why do I get a <code>StackOverflowError</code> during code coverage analysis?</h3>
@@ -191,8 +191,8 @@
   data is collected. Except for technical corner cases these options are
   normally not required. If you exclude classes, no execution data is collected
   for them.
-</p> 
-<p>  
+</p>
+<p>
   Report creation is a separate step where all class files which should show up
   in the report are explicitly provided. Coverage is determined from the
   provided execution data. If execution data is missing for a particular class,
@@ -202,7 +202,7 @@
 
 <p>
   If you want to exclude classes from the report please configure the
-  respective report generation tool accordingly. 
+  respective report generation tool accordingly.
 </p>
 
 </div>
diff --git a/org.jacoco.doc/docroot/doc/flow.html b/org.jacoco.doc/docroot/doc/flow.html
index f320cdc6..d194bc1a 100644
--- a/org.jacoco.doc/docroot/doc/flow.html
+++ b/org.jacoco.doc/docroot/doc/flow.html
@@ -16,7 +16,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Control Flow Analysis</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Control Flow Analysis for Java Methods</h1>
 
@@ -31,7 +31,7 @@
 
 <h2>Control Flow Graphs for Java Bytecode</h2>
 
-<p> 
+<p>
   As an starting point we take the following example method that contains a
   single branching point:
 </p>
@@ -55,7 +55,7 @@ public static void example() {
   <code>IFEQ</code> or the unconditional <code>GOTO</code> opcode. The jump
   targets are technically relative offsets to the target instruction. For better
   readability we use symbolic labels (<code>L1</code>, <code>L2</code>) instead
-  (also the ASM API uses such symbolic labels):  
+  (also the ASM API uses such symbolic labels):
 </p>
 
 <pre class="source linenums">
@@ -87,7 +87,7 @@ public static example()V
   the following Edges. Each edge connects a source instruction with a target
   instruction. In some cases the source instruction or the target instruction
   does not exist (virtual edges for method entry and exit) or cannot be
-  exactly specified (exception handlers). 
+  exactly specified (exception handlers).
 </p>
 
 <table class="coverage">
@@ -108,7 +108,7 @@ public static example()V
     </tr>
     <tr>
       <td>SEQUENCE</td>
-      <td>Instruction, except <code>GOTO</code>, <code>xRETURN</code>, 
+      <td>Instruction, except <code>GOTO</code>, <code>xRETURN</code>,
         <code>THROW</code>, <code>TABLESWITCH</code> and <code>LOOKUPSWITCH</code></td>
       <td>Subsequent instruction</td>
       <td></td>
@@ -167,7 +167,7 @@ public static example()V
 
 <p>
   If a probe has been executed we know that the corresponding edge has been
-  visited. From this edge we can conclude to other preceding nodes and edges: 
+  visited. From this edge we can conclude to other preceding nodes and edges:
 </p>
 
 <ul>
@@ -180,7 +180,7 @@ public static example()V
 <p>
   Recursively applying these rules allows to determine the execution status of
   all instructions of a method &ndash; given that we have probes at the right
-  positions. Therefore JaCoCo inserts probes      
+  positions. Therefore JaCoCo inserts probes
 </p>
 
 <ul>
@@ -212,7 +212,7 @@ public static example()V
       <td><img src="resources/flow-sequence-probe.png" alt="Sequence with Probe"/></td>
       <td>
         In case of a simple sequence the probe is simply inserted between the
-        two instructions. 
+        two instructions.
       </td>
     </tr>
     <tr>
@@ -349,7 +349,7 @@ BASTORE
   The size of the probe code above depends on the position of the probe array
   variable and the value of the probe identifier as different opcodes can be
   used. As calculated in the table below the overhead per probe ranges between 4
-  and 7 bytes of additional bytecode: 
+  and 7 bytes of additional bytecode:
 </p>
 
 <table class="coverage">
@@ -409,7 +409,7 @@ BASTORE
   total classes instrumented with JaCoCo increase their size by about 30%. Due
   to the fact that probe execution does not require any method calls, only local
   instructions, the observed execution time overhead for instrumented
-  applications typically is less than 10%. 
+  applications typically is less than 10%.
 </p>
 
 <h2>References</h2>
diff --git a/org.jacoco.doc/docroot/doc/implementation.html b/org.jacoco.doc/docroot/doc/implementation.html
index 58a5b674..2a11f756 100644
--- a/org.jacoco.doc/docroot/doc/implementation.html
+++ b/org.jacoco.doc/docroot/doc/implementation.html
@@ -16,7 +16,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Implementation Design</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Implementation Design</h1>
 
@@ -38,7 +38,7 @@
   Coverage information has to be collected at runtime. For this purpose JaCoCo
   creates instrumented versions of the original class definitions. The
   instrumentation process happens on-the-fly during class loading using so
-  called Java agents.  
+  called Java agents.
 </p>
 
 <p>
@@ -71,12 +71,12 @@
   The Java agent is loaded by the application class loader. Therefore the
   classes of the agent live in the same name space like the application classes
   which can result in clashes especially with the third party library ASM. The
-  JoCoCo build therefore moves all agent classes into a unique package.  
+  JoCoCo build therefore moves all agent classes into a unique package.
 </p>
 
 <p>
   The JaCoCo build renames all classes contained in the
-  <code>jacocoagent.jar</code> into classes with a 
+  <code>jacocoagent.jar</code> into classes with a
   <code>org.jacoco.agent.rt_&lt;randomid&gt;</code> prefix, including the
   required ASM library classes. The identifier is created from a random number.
   As the agent does not provide any API, no one should be affected by this
@@ -131,7 +131,7 @@
   the presented figures are extracted from a valid test target. A hash code of
   the class definitions allows to differentiate between classes and versions of
   classes. The CRC64 hash computation is simple and fast resulting in a small 64
-  bit identifier. 
+  bit identifier.
 </p>
 
 <p>
@@ -144,7 +144,7 @@
   results. The CRC64 code might produce so called <i>collisions</i>, i.e.
   creating the same hash code for two different classes. Although CRC64 is not
   cryptographically strong and collision examples can be easily computed, for
-  regular class files the collision probability is very low. 
+  regular class files the collision probability is very low.
 </p>
 
 <h2>Coverage Runtime Dependency</h2>
@@ -152,19 +152,19 @@
 <p class="intro">
   Instrumented code typically gets a dependency to a coverage runtime which is
   responsible for collecting and storing execution data. JaCoCo uses JRE types
-  only in generated instrumentation code. 
+  only in generated instrumentation code.
 </p>
 
 <p>
   Making a runtime library available to all instrumented classes can be a
   painful or impossible task in frameworks that use their own class loading
   mechanisms. Since Java 1.6 <code>java.lang.instrument.Instrumentation</code>
-  has an API to extends the bootsstrap loader. As our minimum target is Java 1.5 
+  has an API to extends the bootsstrap loader. As our minimum target is Java 1.5
   JaCoCo decouples the instrumented classes and the coverage runtime through
   official JRE API types only. The instrumented classes communicate through the
   <code>Object.equals(Object)</code> method with the runtime. A instrumented
   class can retrieve its probe array instance with the following code. Note
-  that only JRE APIs are used:   
+  that only JRE APIs are used:
 </p>
 
 
@@ -172,7 +172,7 @@
 Object access = ...                          // Retrieve instance
 
 Object[] args = new Object[3];
-args[0] = Long.valueOf(8060044182221863588); // class id 
+args[0] = Long.valueOf(8060044182221863588); // class id
 args[1] = "com/example/MyClass";             // class name
 args[2] = Integer.valueOf(24);               // probe count
 
@@ -199,17 +199,17 @@ boolean[] probes = (boolean[]) args[0];
     parameter array instead of a <code>equals()</code> method. The coverage
     runtime registers a custom <code>Handler</code> to receive the parameter
     array. This approach might break environments that install their own log
-    managers (e.g. Glassfish).</li> 
+    managers (e.g. Glassfish).</li>
   <li><b><code>URLStreamHandlerRuntime</code></b>: This runtime registers a
     <code>URLStreamHandler</code> for a "jacoco-xxxxx" protocol. Instrumented
     classes open a connection on this protocol. The returned connection object
     is the one that provides access to the coverage runtime through its
     <code>equals()</code> method. However to register the protocol the runtime
-    needs to access internal members of the <code>java.net.URL</code> class.</li> 
+    needs to access internal members of the <code>java.net.URL</code> class.</li>
   <li><b><code>ModifiedSystemClassRuntime</code></b>: This approach adds a
     public static field to an existing JRE class through instrumentation. Unlike
     the other methods above this is only possible for environments where a Java
-    agent is active.</li> 
+    agent is active.</li>
   <li><b><code>InjectedClassRuntime</code></b>: This approach defines a new class
     using <code>java.lang.invoke.MethodHandles.Lookup.defineClass</code>
     introduced in Java 9.</li>
@@ -233,14 +233,14 @@ boolean[] probes = (boolean[]) args[0];
   Coverage analysis for huge projects with several thousand classes or hundred
   thousand lines of code should be possible. To allow this with reasonable
   memory usage the coverage analysis is based on streaming patterns and
-  "depth first" traversals.  
+  "depth first" traversals.
 </p>
 
 <p>
   The complete data tree of a huge coverage report is too big to fit into a
   reasonable heap memory configuration. Therefore the coverage analysis and
   report generation is implemented as "depth first" traversals. Which means that
-  at any point in time only the following data has to be held in working memory:  
+  at any point in time only the following data has to be held in working memory:
 </p>
 
 <ul>
@@ -252,7 +252,7 @@ boolean[] probes = (boolean[]) args[0];
 
 <p class="intro">
   The Java language and the Java VM use different String representation formats
-  for Java elements. For example while a type reference in Java reads like 
+  for Java elements. For example while a type reference in Java reads like
   <code>java.lang.Object</code>, the VM references the same type as
   <code>Ljava/lang/Object;</code>. The JaCoCo API is based on VM identifiers only.
 </p>
@@ -275,7 +275,7 @@ boolean[] probes = (boolean[]) args[0];
 <p>
   Using OSGi bundles allows well defined dependencies at development time and
   at runtime in OSGi containers. As there are no dependencies on OSGi, the
-  bundles can also be used like regular JAR files.  
+  bundles can also be used like regular JAR files.
 </p>
 
 </div>
diff --git a/org.jacoco.doc/docroot/doc/index.html b/org.jacoco.doc/docroot/doc/index.html
index 9efcd966..10129346 100644
--- a/org.jacoco.doc/docroot/doc/index.html
+++ b/org.jacoco.doc/docroot/doc/index.html
@@ -13,7 +13,7 @@
   <a href="../index.html" class="el_report">JaCoCo</a> &gt;
   <span class="el_group">Documentation</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Documentation</h1>
 
diff --git a/org.jacoco.doc/docroot/doc/integrations.html b/org.jacoco.doc/docroot/doc/integrations.html
index 1cd9f5d6..32139e6e 100644
--- a/org.jacoco.doc/docroot/doc/integrations.html
+++ b/org.jacoco.doc/docroot/doc/integrations.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Integration Matrix</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Integration Matrix</h1>
 
@@ -65,7 +65,7 @@
     </tr>
   </tbody>
 </table>
-   
+
 <h3>Third-Party Integrations</h3>
 
 <table class="coverage">
diff --git a/org.jacoco.doc/docroot/doc/license.html b/org.jacoco.doc/docroot/doc/license.html
index 126fcf8e..4159b442 100644
--- a/org.jacoco.doc/docroot/doc/license.html
+++ b/org.jacoco.doc/docroot/doc/license.html
@@ -13,13 +13,13 @@
   <a href="../index.html" class="el_report">JaCoCo</a> &gt;
   <span class="el_source">License</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>License</h1>
 
 <p>
   Copyright &copy; ${copyright.years} Mountainminds GmbH &amp; Co. KG and Contributors
-</p> 
+</p>
 
 <p>
   The JaCoCo Java Code Coverage Library and all included documentation is made
@@ -39,7 +39,7 @@
   trademark, registered trademark, or service mark of The OSGi Alliance in the
   US and other countries. Apache Ant and Apache Maven are trademarks of the
   Apache Software Foundation. Android and Dalvik are trademarks of Google Inc.
-  All other trademarks are the property of their respective owners. 
+  All other trademarks are the property of their respective owners.
 </p>
 
 
diff --git a/org.jacoco.doc/docroot/doc/maven.html b/org.jacoco.doc/docroot/doc/maven.html
index 98c565b5..4e41e4d4 100644
--- a/org.jacoco.doc/docroot/doc/maven.html
+++ b/org.jacoco.doc/docroot/doc/maven.html
@@ -16,7 +16,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Maven Plug-in</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Maven Plug-in</h1>
 
@@ -45,7 +45,7 @@
 
 <ul>
   <li>
-    The JaCoCo distribution contains a simple example how code coverage 
+    The JaCoCo distribution contains a simple example how code coverage
     can be added to a Maven project.</li>
   <li>
     This <a href="examples/build/pom.xml">POM file</a>
diff --git a/org.jacoco.doc/docroot/doc/mission.html b/org.jacoco.doc/docroot/doc/mission.html
index 1c444792..f5098ec1 100644
--- a/org.jacoco.doc/docroot/doc/mission.html
+++ b/org.jacoco.doc/docroot/doc/mission.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Mission</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Mission</h1>
 
@@ -22,7 +22,7 @@
   JaCoCo should provide the standard technology for code coverage analysis in
   Java VM based environments. The focus is providing a lightweight, flexible and
   well documented library for integration with various build and development
-  tools. 
+  tools.
 </p>
 
 <p>
@@ -43,7 +43,7 @@
   Therefore we started the JaCoCo project to provide a new standard technology
   for code coverage analysis in Java VM based environments. The focus is
   providing a lightweight, flexible and well documented library for integration
-  with various build and development tools. <a href="ant.html">Ant tasks</a>, a 
+  with various build and development tools. <a href="ant.html">Ant tasks</a>, a
   <a href="maven.html">Maven plug-in</a> and the
   <a href="http://www.eclemma.org/">EclEmma Eclipse plug-in</a> are provided as
   reference usage scenarios. Also many other tool vendors and Open Source
diff --git a/org.jacoco.doc/docroot/doc/offline.html b/org.jacoco.doc/docroot/doc/offline.html
index c29c098d..b1f184bd 100644
--- a/org.jacoco.doc/docroot/doc/offline.html
+++ b/org.jacoco.doc/docroot/doc/offline.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Offline Instrumentation</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Offline Instrumentation</h1>
 
@@ -64,7 +64,7 @@
 <p>
   In both cases configuration values may contain variables in the format
   <code>${<i>name</i>}</code> which are resolved with system property values
-  at runtime. For example: 
+  at runtime. For example:
 </p>
 
 <pre class="source">
@@ -79,7 +79,7 @@ destfile=${user.home}/jacoco.exec
   instrumented classes. The proper location for <code>jacocoagent.jar</code>
   might depend on your deployment scenario. The first instrumented class loaded
   will trigger the initialization of the JaCoCo runtime. If no instrumented
-  class is loaded the JaCoCo runtime will not get started at all.   
+  class is loaded the JaCoCo runtime will not get started at all.
 </p>
 
 <h2>Using Pre-Instrumented Classes With the Java Agent</h2>
@@ -88,7 +88,7 @@ destfile=${user.home}/jacoco.exec
   agent. In this case the configuration is taken from the agent options. The
   agent must be configured in a way that pre-instrumented classes are excluded,
   e.g. with "<code>excludes=*</code>". Otherwise it will result in error
-  messages on the console if the agent instruments such classes again. 
+  messages on the console if the agent instruments such classes again.
 </p>
 
 <h2>Execution Data Collection</h2>
diff --git a/org.jacoco.doc/docroot/doc/repo.html b/org.jacoco.doc/docroot/doc/repo.html
index 2f36dcc4..be517de1 100644
--- a/org.jacoco.doc/docroot/doc/repo.html
+++ b/org.jacoco.doc/docroot/doc/repo.html
@@ -16,14 +16,14 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Maven Repository</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Maven Repository</h1>
 
 <p>
   If you want to integrate JaCoCo within your tools you might directly retrieve
   it from the Maven repository. There are two repositories, one for JaCoCo
-  releases, one for regular snapshot builds.   
+  releases, one for regular snapshot builds.
 </p>
 
 <table class="coverage">
diff --git a/org.jacoco.doc/docroot/doc/resources/doc.css b/org.jacoco.doc/docroot/doc/resources/doc.css
index ec89c32a..592be8ab 100644
--- a/org.jacoco.doc/docroot/doc/resources/doc.css
+++ b/org.jacoco.doc/docroot/doc/resources/doc.css
@@ -43,7 +43,7 @@ div#content a[href^='http://'], a[href^='https://'] {
   background:transparent url(extern.gif) center left no-repeat;
 }
 
-/* === Definitions from report.css start here: === */ 
+/* === Definitions from report.css start here: === */
 
 body, td {
   font-family:sans-serif;
@@ -148,7 +148,7 @@ pre.source span.pc {
 
 table.coverage {
   empty-cells:show;
-  border-collapse:collapse; 
+  border-collapse:collapse;
 }
 
 table.coverage thead {
@@ -178,7 +178,7 @@ table.coverage tbody td {
   border-bottom:#d6d3ce 1px solid;
 }
 
-table.coverage tbody tr:hover { 
+table.coverage tbody tr:hover {
   background: #f0f0d0 !important;
 }
 
diff --git a/org.jacoco.doc/docroot/doc/support.html b/org.jacoco.doc/docroot/doc/support.html
index aea53db2..f705250f 100644
--- a/org.jacoco.doc/docroot/doc/support.html
+++ b/org.jacoco.doc/docroot/doc/support.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Support and Feedback</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Support and Feedback</h1>
 
diff --git a/org.jacoco.doc/docroot/doc/team.html b/org.jacoco.doc/docroot/doc/team.html
index 14a8b1b6..6f3d5e76 100644
--- a/org.jacoco.doc/docroot/doc/team.html
+++ b/org.jacoco.doc/docroot/doc/team.html
@@ -14,7 +14,7 @@
   <a href="index.html" class="el_group">Documentation</a> &gt;
   <span class="el_source">Team</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>Team</h1>
 
@@ -29,9 +29,9 @@
 </ul>
 
 <p>
-  To keep the development process open please use the 
+  To keep the development process open please use the
   <a href="support.html">public communication channels</a> and do not contact
-  individual team members. 
+  individual team members.
 </p>
 
 <h2>Former Developers</h2>
diff --git a/org.jacoco.doc/docroot/index.html b/org.jacoco.doc/docroot/index.html
index 34eb240f..e7a6cbe7 100644
--- a/org.jacoco.doc/docroot/index.html
+++ b/org.jacoco.doc/docroot/index.html
@@ -12,7 +12,7 @@
 <div class="breadcrumb">
   <span class="el_report">JaCoCo</span>
 </div>
-<div id="content"> 
+<div id="content">
 
 <h1>JaCoCo - Java Code Coverage Library</h1>
 
diff --git a/org.jacoco.doc/javadoc/overview.html b/org.jacoco.doc/javadoc/overview.html
index 1f3c288f..7da2c67d 100644
--- a/org.jacoco.doc/javadoc/overview.html
+++ b/org.jacoco.doc/javadoc/overview.html
@@ -10,15 +10,15 @@
 
 <h1>Bundle org.jacoco.core</h1>
 
-<p>  
+<p>
   The core bundle implements the code coverage technology itself. It provides
   APIs and implementation for
 </p>
 
-<ul>  
+<ul>
   <li>class file instrumentation,</li>
-  <li>collecting execution data at runtime and</li> 
-  <li>analyzing coverage data.</li> 
+  <li>collecting execution data at runtime and</li>
+  <li>analyzing coverage data.</li>
 </ul>
 
 <h1>Bundle org.jacoco.agent</h1>
diff --git a/org.jacoco.report/src/org/jacoco/report/internal/html/resources/prettify.js b/org.jacoco.report/src/org/jacoco/report/internal/html/resources/prettify.js
index ab278821..b2766fe0 100644
--- a/org.jacoco.report/src/org/jacoco/report/internal/html/resources/prettify.js
+++ b/org.jacoco.report/src/org/jacoco/report/internal/html/resources/prettify.js
@@ -1112,7 +1112,7 @@ window['_pr_isIE6'] = function () {
       for (var i = 0; i < 10; ++i) {
         lineBreaks[i] = lineBreakHtml + '</li><li class="L' + i + '">';
       }
-      var lineNum = numberLines[1] && numberLines[1].length 
+      var lineNum = numberLines[1] && numberLines[1].length
           ? numberLines[1] - 1 : 0;  // Lines are 1-indexed
       html.push('<ol class="linenums"><li class="L', (lineNum) % 10, '"');
       if (lineNum) {
@@ -1403,7 +1403,7 @@ window['_pr_isIE6'] = function () {
                      Infinity);
       for (; k < elements.length && clock.now() < endTime; k++) {
         var cs = elements[k];
-        // [JACOCO] 'prettyprint' -> 'source' 
+        // [JACOCO] 'prettyprint' -> 'source'
         if (cs.className && cs.className.indexOf('source') >= 0) {
           // If the classes includes a language extensions, use it.
           // Language extensions can be specified like
@@ -1418,7 +1418,7 @@ window['_pr_isIE6'] = function () {
           for (var p = cs.parentNode; p; p = p.parentNode) {
             if ((p.tagName === 'pre' || p.tagName === 'code' ||
                  p.tagName === 'xmp') &&
-                // [JACOCO] 'prettyprint' -> 'source' 
+                // [JACOCO] 'prettyprint' -> 'source'
                 p.className && p.className.indexOf('source') >= 0) {
               nested = true;
               break;
diff --git a/org.jacoco.report/src/org/jacoco/report/internal/html/resources/report.css b/org.jacoco.report/src/org/jacoco/report/internal/html/resources/report.css
index 08eba792..dd936bca 100644
--- a/org.jacoco.report/src/org/jacoco/report/internal/html/resources/report.css
+++ b/org.jacoco.report/src/org/jacoco/report/internal/html/resources/report.css
@@ -137,7 +137,7 @@ pre.source span.bpc:hover {
 
 table.coverage {
   empty-cells:show;
-  border-collapse:collapse; 
+  border-collapse:collapse;
 }
 
 table.coverage thead {
@@ -185,7 +185,7 @@ table.coverage tbody td {
   border-bottom:#d6d3ce 1px solid;
 }
 
-table.coverage tbody tr:hover { 
+table.coverage tbody tr:hover {
   background: #f0f0d0 !important;
 }
 
diff --git a/org.jacoco.report/src/org/jacoco/report/internal/html/resources/sort.js b/org.jacoco.report/src/org/jacoco/report/internal/html/resources/sort.js
index f323bdb8..34179d2d 100644
--- a/org.jacoco.report/src/org/jacoco/report/internal/html/resources/sort.js
+++ b/org.jacoco.report/src/org/jacoco/report/internal/html/resources/sort.js
@@ -8,7 +8,7 @@
  *
  * Contributors:
  *    Marc R. Hoffmann - initial API and implementation
- *    
+ *
  *******************************************************************************/
 
 (function () {
@@ -18,8 +18,8 @@
    *
    * @param linkelementids
    *          list of element ids to search for links to add sort inidcator
-   *          hash links   
-   */  
+   *          hash links
+   */
   function initialSort(linkelementids) {
     window.linkelementids = linkelementids;
     var hash = window.location.hash;
@@ -45,7 +45,7 @@
 
   /**
    * Sorts the columns with the given header dependening on the current sort state.
-   */  
+   */
   function toggleSort(header) {
     var sortup = header.className.indexOf('down ') == 0;
     sortColumn(header, sortup);
@@ -53,23 +53,23 @@
 
   /**
    * Sorts the columns with the given header in the given direction.
-   */  
+   */
   function sortColumn(header, sortup) {
     var table = header.parentNode.parentNode.parentNode;
     var body = table.tBodies[0];
     var colidx = getNodePosition(header);
-    
+
     resetSortedStyle(table);
-    
+
     var rows = body.rows;
     var sortedrows = [];
     for (var i = 0; i < rows.length; i++) {
       r = rows[i];
       sortedrows[parseInt(r.childNodes[colidx].id.slice(1))] = r;
     }
-    
+
     var hash;
-    
+
     if (sortup) {
       for (var i = sortedrows.length - 1; i >= 0; i--) {
         body.appendChild(sortedrows[i]);
@@ -83,7 +83,7 @@
       header.className = 'down ' + header.className;
       hash = 'dn-' + header.id;
     }
-    
+
     setHash(hash);
   }
 
@@ -109,14 +109,14 @@
         var hashpos = href.indexOf("#");
         if (hashpos != -1) {
             href = href.substring(0, hashpos);
-        } 
+        }
         a.href = href + "#" + hash;
     }
   }
 
   /**
    * Calculates the position of a element within its parent.
-   */  
+   */
   function getNodePosition(element) {
     var pos = -1;
     while (element) {
@@ -141,7 +141,7 @@
       }
     }
   }
-  
+
   window['initialSort'] = initialSort;
   window['toggleSort'] = toggleSort;