Fixed an issue where an extra line of the stack trace was being printed by the ThrowableProxyConverter when specifying a length option.
Removed the given/when/then comments, as they're not in keeping with existing tests.
Removes redundant and forever dangling connection

The DataSourceConnectionSource.start() method opens a new connection
only to determine whether or not the discoverConnectionProperties()
should be called. This is unnecessary since that method will perform
the same check and issue a very similar warning. A more serious
problem is that the connection is never closed.

This commit removes the use of this extra connection completely. I
think this is the last issue in need of a fix before LOGBACK-376 can
be closed.
fixing table name to lower case and correcting version of mysql
Should be able to look up Boolean, for example.
fix for LOGBACK-743

Wrapped the call to System.getProperty in a try/catch to anticipate
the SecurityException that can result from accessing system properties
in the presence of a SecurityManager (e.g. in an applet sandbox).
Merge pull request #128 from thallgren/LOGBACK-376

Removes redundant and forever dangling connection
Merge pull request #129 from jampow/master

Fixed MySQL setup script to use lower-case table name to match the references in the file. This had caused an error on systems where case sensitivity matters.
Merge pull request #138 from kovacevicm/patch-1

Fixed JNDI lookup of non-String entries
Merge pull request #25 from jon-ruckwood/throwable-proxy-converter-fix

LBCORE-179: Fix regarding incorrect stack trace depth when specifying %throwable with argument
Merge pull request #143 from kovacevicm/master

Avoid NPE during JNDI lookup
Merge pull request #4 from rkapsi/master

Use append instead of concatenate
Removes redundant and forever dangling connection

The DataSourceConnectionSource.start() method opens a new connection
only to determine whether or not the discoverConnectionProperties()
should be called. This is unnecessary since that method will perform
the same check and issue a very similar warning. A more serious
problem is that the connection is never closed.

This commit removes the use of this extra connection completely. I
think this is the last issue in need of a fix before LOGBACK-376 can
be closed.
fixing table name to lower case and correcting version of mysql
Should be able to look up Boolean, for example.
Fixed an issue where an extra line of the stack trace was being printed by the ThrowableProxyConverter when specifying a length option.
Removed the given/when/then comments, as they're not in keeping with existing tests.
Merge pull request #143 from kovacevicm/master

Avoid NPE during JNDI lookup
Merge pull request #4 from rkapsi/master

Use append instead of concatenate
Fix exception for logger name with '.' and '$'

LOGBACK-384 - Mixing periods and dollar signs in a logger
name causes IllegalArgumentException from LoggerFactory.getLogger

Fixing the logic to treat '$' and '.' at same level as per
comment [1]. Also adding a testcase

[1] http://jira.qos.ch/browse/LOGBACK-384?focusedCommentId=13105&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13105