[
https://issues.apache.org/jira/browse/AVRO-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992234#comment-12992234
]
Scott Carey commented on AVRO-758:
----------------------------------
Since the tools jar is intended to run stand-alone, it has to have an slf4j
binding in it.
If you intend to use avro in a project, you'll want to include the component
avro jars depending on what features you need. This way you can control the
dependencies and anything common that might collide like slf4j. The tools-jar
isn't going to work in the classpath of most projects, since it has all of the
dependencies inside of it.
The slf4j-log4j12-1.6.1.jar in your classpath is not from avro, and may not be
compatible with Avro's 1.5.x slf4j. Usually slf4j happily functions with only
a warning when you have multiple jars, but I haven't tried mixing 1.5.x and
1.6.x.
We definitely should get rid of the junk that hadoop-jar is pulling into
toolsjar: log4j, its shell scripts, and other stuff.
> 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
