Message-ID: <1422019536.300536.1369055975192.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_300535_253545450.1369055974721" ------=_Part_300535_253545450.1369055974721 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
BTM ships with SLF4J which is a logging facade much like Apache Comm= ons Logging but it's safe to use in application servers unlike Commons Logg= ing which suffers from complex classloader issues.
Much like Commons Logging, SLF4J can route the log requests to many diff= erent implementations including the two most common ones: JDK 1.4 and Log4J.
By default, BTM is shipped with slf4j-jdk14-1.4.3.jar which is the the <= a href=3D"http://jcp.org/aboutJava/communityprocess/review/jsr047/" class= =3D"external-link" rel=3D"nofollow">JSR 047 logging API (aka JDK 1.4 loggin= g) wrapper. If you want to use another logger, simply delete the slf4j-= jdk14-1.4.3.jar file and replace it with any one from this list:
You will also need to put the slf4j-api-1.4.3.jar file in your classpath as well, no matter= which one of the above jars you choose.
Those jars come from the 1.4.3 distribution of SLF4J.