Github user dsbos commented on the pull request:
https://github.com/apache/drill/pull/116#issuecomment-137811250
Would it be better if the JDBC-all Jar file didn't contain a logback.xml
file?
If the JDBC-all Jar doesn't already have that file, then to configure
logback differently with their own logback.xml file, users only have to get
their own file on the classpath _somewhere_.
However, if the JDBC-all Jar does already have that file, it seems that
users will have to get their logback.xml file on the class path _before_ the
JDBC-all Jar file (right?). Although sometimes that's trivial, when the class
path is set by, say, listing all .jar files in a lib/ directory (e.g., as in
Tomcat for Spotfire), controlling the order might not be possible or easy.
(A solution to keep the contents of the logback.xml file (as a convenient
starting point for the user to copy out and modify) in the JDBC-all JAR file
but not really have an active/interfering actual logback.xml file would be to
use a modified name (e.g, logback-example.xml).)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
