Bug #59511 Class com.mysql.jdbc.log.Log4JLogger removed from Connector/J in 5.1.14

• Submitted: 14 Jan 2011 18:06
• Modified: 10 Mar 2011 10:58
• Reporter: Brett Delle Grazie
• Status: Closed
• Category: Connector / J
• Severity: S3 (Non-critical)
• Version: 5.1.14
• OS: Any
• Assigned to: Tony Bedford
• CPU Architecture: Any

[14 Jan 2011 18:06] Brett Delle Grazie

Description:
Optional logging class:
com.mysql.jdbc.log.Log4JLogger

Does not appear to be in the source/binary package for 5.1.14.

This class was present (and useful) in 5.1.13

How to repeat:
Download, check for com.mysql.jdbc.log.Log4JLogger class (not present)

Suggested fix:
Please put it back from 5.1.13

[14 Jan 2011 18:12] Mark Matthews

5.1.15 will ship with an SLF4J Logger (which can then be plugged into Log4j). Unfortunately we can't ship a direct log4j integration because the FSF says the GPL isn't compatibile with Log4J's license.

You can get nightly snapshots of Connector/J that already contain this change from http://downloads.mysql.com/snapshots.php

[10 Mar 2011 10:58] Tony Bedford

An entry has been added to the 5.1.15 changelog: 

        Optional logging class 
        com.mysql.jdbc.log.Log4JLogger was not 
        included in the source/binary package for 5.1.14. 

        5.1.15 will ship with an SLF4J logger (which can then be 
        plugged into Log4J). Unfortunately, it is not possible to ship a 
        direct Log4J integration because the GPL is not compatibile with 
        Log4J's license.