[
https://issues.apache.org/jira/browse/CALCITE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115902#comment-15115902
]
Julian Hyde edited comment on CALCITE-669 at 1/25/16 8:18 PM:
--------------------------------------------------------------
[~elserj], Yes, commits are open following the release, and you can use your
discretion as a committer. You'll probably hit a conflict in pom.xml due to
CALCITE-999
https://github.com/apache/calcite/commit/4d58768d35d5accbf7330d10b91f2541b6f1ab38.
was (Author: julianhyde):
[~elserj], Yes, commits are open following the release, and you can use your
discretion as a committer. You'll probably hit a conflict in pom.xml due to
CALCITE-699
https://github.com/apache/calcite/commit/4d58768d35d5accbf7330d10b91f2541b6f1ab38.
> Move from Commons Logging to SLF4J
> ----------------------------------
>
> Key: CALCITE-669
> URL: https://issues.apache.org/jira/browse/CALCITE-669
> Project: Calcite
> Issue Type: Task
> Components: avatica
> Reporter: Nick Dimiduk
> Assignee: Josh Elser
> Priority: Minor
> Fix For: 1.7.0
>
>
> As mentioned on CALCITE-641, it could be useful to adopt a logging
> implementation that supports pluggable backends and has
> [MDC|http://www.slf4j.org/manual.html#mdc] support.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
