[
https://issues.apache.org/jira/browse/AVRO-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992217#comment-12992217
]
Stu Hood commented on AVRO-758:
-------------------------------
Actually, removing the log4j.properties has not fixed the problem: it looks
like including SLF4J in the tools jar is the culprit.
{noformat}SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/Users/stuhood/src/cassandra/working/lib/avro-tools-1.5.0-SNAPSHOT~r1068142+AVRO-757.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/Users/stuhood/src/cassandra/working/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
explanation.{noformat}
> avro-tools jar contains log4j config
> ------------------------------------
>
> Key: AVRO-758
> URL: https://issues.apache.org/jira/browse/AVRO-758
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.5.0
> Reporter: Stu Hood
> Priority: Minor
> Fix For: 1.5.0
>
>
> The avro-tools jar generated on trunk contains a log4j config that can
> override the defaults of projects that include it.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
