doc edits

Signed-off-by: Ceki Gulcu <ceki@qos.ch>

pom.xml

@@ -33,7 +33,7 @@
   </scm>  
 
   <properties>
-    <latest.stable.version>1.7.35</latest.stable.version>
+    <latest.stable.version>1.7.36</latest.stable.version>
     <latest.2.version>2.0.0-alpha6</latest.2.version>    
     <!-- java.util.ServiceLoader requires Java 6 -->
     <jdk.version>8</jdk.version>

slf4j-site/src/site/pages/codes.html

@@ -513,6 +513,34 @@ class B extends A {
     href="legacy.html">Bridging legacy APIs</a>.
     </p>
 
+    <!-- ====================================================== -->
+    <h3 class="doAnchor" name="no_tlm">Exception in
+    thread "main" java.lang.NoSuchFieldError: tlm</h3>
+
+    <pre class="prettyprint source">
+      Exception in thread "main" java.lang.NoSuchFieldError: tlm
+	at org.apache.log4j.MDCFriend.fixForJava9(MDCFriend.java:11)
+	at org.slf4j.impl.Log4jMDCAdapter.<clinit>(Log4jMDCAdapter.java:38)
+	at Main.main(Main.java:5) </pre>
+
+    <p>The <code>NoSuchFieldError</code> is thrown
+    when <em>slf4j-log4j12</em> attempts to access the 'tlm' package
+    private field in <code>org.apache.log4j.MDC</code> which was
+    specified as being of type
+      <em>java.lang.Object</em> in log4j 1.2.x but was changed
+      to <em>java.lang.ThreadLocal</em> in reload4j. Moreover, such
+      access to package private fields from different modules is not
+      authorized by default in modularized applications in Java 9 and
+      later.</p>
+
+    <p>To keep a long story short, the <code>NoSuchFieldError</code>
+    can be avoided by using <em>slf4j-reload4j.jar</em>
+    with <em>reload4j.jar</e>. Stated
+    differently, <code>org.slf4j.MDC</code> <b>cannot</b> be used with
+    the <em>slf4j-log4j12.jar</em> and <em>reload4j.jar</em>
+    combination.</p>
+    
+    
     <!-- ====================================================== -->
 
     <h3 class="doAnchor" name="no_static_mdc_binder">Failed to load

slf4j-site/src/site/pages/download.html

@@ -33,7 +33,7 @@
 
       <h2>EXPERIMENTAL/UNSTABLE version</h2>
 
-      <p>SLF4J version <span class="big">${project.version}</span> is
+      <p>SLF4J version <span class="big">${latest.2.version}</span> is
       the most recent but it is also experimental/unstable.</p>
 
       <h2>Maven central</h2>

slf4j-site/src/site/pages/manual.html

@@ -278,8 +278,7 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail
         <em>slf4j-reload4j</em> module at <b>build time</b>.</span>
         Assuming you wish to continue to use the log4j 1.x framework,
         we strongly encourage you to use <code>slf4j-reload4j</code>
-        instead. See below.
-        <p/>
+        instead. See below.  <p/>
 
         </dd>
 
@@ -289,9 +288,9 @@ SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail
         <a href="http://reload4j.qos.ch">reload4j</a>
         framework. Reload4j is a drop-in replacement for log4j version
         1.2.7. You also need to place <em>reload4j.jar</em> on your
-        class path.<p/></dd>
+        class path.</p>
 
-        
+       
         <dt><em>slf4j-jdk14-${latest.stable.version}.jar</em> </dt>
         <dd>Binding/provider for java.util.logging, also referred to as JDK 1.4
         logging <p/></dd>

slf4j-site/src/site/pages/news.html

@@ -40,6 +40,34 @@
      class names in <code/>
    -->
 
+   <!-- 
+   <hr noshade="noshade" size="1"/>
+   
+   <h3>2022-0 - Release of SLF4J 2.0.0-alpha7</h3>
+
+   <p>Correct corrupt "Export-Package" declaration in
+   <em>MANIFEST.MF</em> in <em>log4j-over-slf4j</em> module. This
+   fixes <a href="https://jira.qos.ch/browse/SLF4J-541">SLF4J-541</a>
+   reported by Flavio Donz&eacute;.</p>
+   -->
+   
+   <hr noshade="noshade" size="1"/>
+   
+   <h3>2022-02-08 - Release of SLF4J 1.7.36</h3>
+
+   <p>Correct corrupt "Export-Package" declaration in
+   <em>MANIFEST.MF</em> in <em>log4j-over-slf4j</em> module. This
+   fixes <a href="https://jira.qos.ch/browse/SLF4J-541">SLF4J-541</a>
+   reported by Flavio Donz&eacute;.</p>
+
+   <p>Starting with version 1.7.36, slf4j releases will be
+   reproducible. By reproducible we mean that anyone checking out the
+   code corresponding to the release version from source code
+   repository and building that local copy, will obtain an identical
+   binary to the published binary.
+   </p>
+   
+   
    <hr noshade="noshade" size="1"/>
    
     <h3>2022-01-25 - Release of SLF4J 1.7.35</h3>

slf4j-site/src/site/pages/templates/header.js

@@ -6,11 +6,6 @@ document.write('      <img src="' + prefix + 'images/logos/slf4j-logo.jpg" alt="
 document.write('       </a>')
 document.write('    </td>')
 
-document.write('   <td style="vertical-align:bottom;">')
-document.write('     <p style="background-color: #fffbd9; border-color: #db4545; border-width: thin;')
-document.write('        border-style: dotted; padding: 5px;">');
-document.write('     Sponsor us for the purchase of dedicated hardware. This will enable the production of automated and <b>isolated</b> releases.</p>');
-document.write('   </td>');
 
 document.write('   <td style="vertical-align:bottom;">');