avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Carey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AVRO-791) Split avro-tools jar in 1.5.0 to one contains avro tool classes and one contains external dependencies
Date Wed, 20 Apr 2011 00:24:05 GMT

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

Scott Carey updated AVRO-791:
-----------------------------

    Attachment: AVRO-791.patch

Patch adds avro-tools-VERSION-nodeps.jar.

This patch also moves the 'sign' portion to a profile, so that users are not forced to sign
in order to 'install' in normal development (add -P sign to do so).

We could move that to another ticket, but signing was introduced without one anyhow.

> 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
>
>         Attachments: AVRO-791.patch
>
>
> 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

Mime
View raw message