Author: ceki Date: Sat Jul 25 09:18:31 2009 New Revision: 1380 Modified: slf4j/trunk/slf4j-site/src/site/pages/codes.html slf4j/trunk/slf4j-site/src/site/pages/faq.html
Log: - removed "IllegalAccessError" entry in codes.html which duplicates a similar entry in faq.html Modified: slf4j/trunk/slf4j-site/src/site/pages/codes.html ============================================================================== --- slf4j/trunk/slf4j-site/src/site/pages/codes.html (original) +++ slf4j/trunk/slf4j-site/src/site/pages/codes.html Sat Jul 25 09:18:31 2009 @@ -104,6 +104,9 @@ href="http://www.slf4j.org/download.html">download page</a>. </p> <!-- ====================================================== --> + <!-- duplicates /faq.html#IllegalAccessError --> + +<!-- <h3> <a name="illegalAccess" href="#illegalAccess">java.lang.IllegalAccessError: tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from class @@ -129,7 +132,7 @@ artifacts. Please also refer to the relevant <a href="faq.html#compatibility">FAQ entry</a>. </p> - +--> <!-- ====================================================== --> <h3> <a name="multiple_bindings" href="#multiple_bindings">Multiple Modified: slf4j/trunk/slf4j-site/src/site/pages/faq.html ============================================================================== --- slf4j/trunk/slf4j-site/src/site/pages/faq.html (original) +++ slf4j/trunk/slf4j-site/src/site/pages/faq.html Sat Jul 25 09:18:31 2009 @@ -381,15 +381,23 @@ org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:60)</pre> + <p>This error is caused by the static initilizer of the + <code>LoggerFactory</code> class attempting to directly access + the SINGLETON field of + <code>org.slf4j.impl.StaticLoggerBinder</code>. While this was + allowed in SLF4J 1.5.5 and earlier, in 1.5.6 and later the + SINGLETON field has been marked as private access. + </p> + + <p>If you get the exception shown above, then you are using an older version of slf4j-api, e.g. 1.4.3, with a new version of a - slf4j binding, e.g. 1.5.6.</p> - - <p>Typically, this occurs when your Maven <em>pom.ml</em> file - incoprporates hibernate 3.3.0 which declares a dependency on - slf4j-api version 1.4.2. If your <em>pom.xml</em> declares a - dependency on an slf4j binding, say slf4j-log4j12 version 1.5.6, - then you will get illegal access errors. + slf4j binding, e.g. 1.5.6. Typically, this occurs when your + Maven <em>pom.ml</em> file incoprporates hibernate 3.3.0 which + declares a dependency on slf4j-api version 1.4.2. If your + <em>pom.xml</em> declares a dependency on an slf4j binding, say + slf4j-log4j12 version 1.5.6, then you will get illegal access + errors. </p> <p>To see which version of slfj4-api is pulled in by Maven, use _______________________________________________ dev mailing list dev@slf4j.org http://www.slf4j.org/mailman/listinfo/dev