[
https://issues.apache.org/jira/browse/AVRO-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992312#comment-12992312
]
Stu Hood commented on AVRO-758:
-------------------------------
> If you intend to use avro in a project, you'll want to include
> the component avro jars depending on what features you need.
It appears that the compiler jar has a dependency on the tools jar: this is why
we needed to pull them both in. I can probably subdivide our classpath to
include the tools jar only at compile time, but this is suboptimal.
> The slf4j-log4j12-1.6.1.jar in your classpath is not from avro
Correct: the Cassandra project is using slf4j for its logging, so adding the
Avro tools jar gave this warning, and resulted in our runtime log settings
being ignored.
----
Whether the tools jar needs to be split a bit more so that the compiler jar
doesn't depend on it, or whether we can remove the embedded slf4j dependency is
my question.
Also, I might have just run the wrong mvn target: I assume when Avro goes into
the maven repos, it isn't in this super-jar form.
> 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
