You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2011/03/30 23:29:06 UTC

[jira] [Updated] (AVRO-791) Split avro-tools jar in 1.5.0 to one contains avro tool classes and one contains external dependencies

     [ https://issues.apache.org/jira/browse/AVRO-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting updated AVRO-791:
------------------------------

    Fix Version/s: 1.5.1

It would be good to fix this in 1.5.1.

> 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