title: Log4j 2.0 and SLF4J and the never ending future of java logging frameworks
body: <p>So I just found out today that Log4J 2.0 is now actively being developed, there is an alpha version and it is said to replace logback.</p>
  
  <p>Right now in my app I have close to 4 maybe more logging frameworks:</p>
  
  <ul>
  <li>Java Util Logging </li>
  <li>log4j </li>
  <li>slf4j</li>
  <li>logback (ignored thanks to a maven provided hack)</li>
  <li>commons logging (ignored thanks to a maven provided hack)</li>
  <li>And tomcat has its own JULI adapter</li>
  </ul>
  
  <p>I have been using log4j (1.2.x) because frankly I just haven't needed the <em>features</em> of the newer guys but I have been tempted lately to switch to SLF4J and mainly <strong>because I don't want to have rewrite my complicated log4j configurations files to a new format</strong> (logback).</p>
  
  <p>Now my question is in terms of what I should code against is SLF4J the right choice for the future given log4j 2.0. </p>
  
  <p><em>It seems like I should just stick with old log4j (<code>1.2.x</code>) as it is the lowest common denominator?</em></p>
  
  <p><strong>UPDATE:</strong> on further examination of log4j 2.0 while very similar it appears the configuration is not backward compatible with log4j 1.2. Looks like logback is the best choice.</p>