[
https://issues.apache.org/jira/browse/AVRO-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013664#comment-13013664
]
Doug Cutting commented on AVRO-791:
-----------------------------------
I don't think we should change the contents or name of avro-tools.jar. It's
convenient to have a single jar that works as a command-line executable.
But I agree that we should add a new jar that contains just the tool
implementations. I needed this recently when updating the java-serialization
benchmark code to use Avro 1.5.0. Perhaps the new jar could be called
avro-tool.jar?
> Split avro-tools jar in 1.5.0 to one contains avro tool classes and one
> contains external dependencies
> ------------------------------------------------------------------------------------------------------
>
> Key: AVRO-791
> URL: https://issues.apache.org/jira/browse/AVRO-791
> Project: Avro
> Issue Type: Wish
> Components: java
> Affects Versions: 1.5.0
> Reporter: Xiaolu Ye
> Fix For: 1.5.1
>
>
> Currently, avro-tools.jar for 1.5.0 contains both avro specific tools classes
> from org.apache.avro.tool and many external dependencies like org.slf4j.impl.
> The problem is that if i define my own logback impl for slf4j in my pom, it
> conflicts with the org.slf4j.impl.StaticLoggerBinder.class in avro-tools. It
> would be better to split it to two jars: one only contains avro specific
> tools, and another one only contains external dependencies
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
