#23: Share execution data porperly if the same class definition is loaded multiple times.
diff --git a/org.jacoco.doc/docroot/doc/implementation.html b/org.jacoco.doc/docroot/doc/implementation.html
index a835f91..39d3865 100644
--- a/org.jacoco.doc/docroot/doc/implementation.html
+++ b/org.jacoco.doc/docroot/doc/implementation.html
@@ -222,14 +222,16 @@
Making a runtime library available to all instrumented classes can be a
painful or impossible task in frameworks that use there own class loading
mechanisms. Therefore JaCoCo decouples the instrumented classes and the
- coverage runtime through official JRE API types. Currently two approaches has
+ coverage runtime through official JRE API types. Currently two approaches have
been implemented:
</p>
<ul>
- <li>Use a shared <code>java.util.logging.Logger</code> instance to report
- coverage data to. The coverage runtime registers a custom
- <code>Handler</code> to receive the data. (Default)</li>
+ <li>By default we use a shared <code>java.util.logging.Logger</code> instance
+ to report coverage data to. The coverage runtime registers a custom
+ <code>Handler</code> to receive the data. The problem with this approach is
+ that the logging framework removes all handlers during shutdown. This may
+ break classes that get initialized during JVM shutdown.</li>
<li>Another approach was to store a <code>java.util.Map</code> instance
under a system property. This solution breaks the contract that system
properties must only contain <code>java.lang.String</code> values and has