[ 
https://issues.apache.org/jira/browse/AVRO-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801822#action_12801822
 ] 

Steve Loughran commented on AVRO-348:
-------------------------------------

The current workaround is to exclude the stuff you don't want when importing 
avro or any hadoop-* artifact into your own ivy project
{code}
    <dependency org="org.apache.hadoop"
                name="avro"
                rev="${avro.version}"
                conf="redist->default">
      <exclude org="com.thoughtworks.paranamer" />
      <exclude org="org.slf4j"/>
      <exclude org="org.mortbay.jetty"/>
    </dependency>
{code}

It would be nice if the optional dependencies were declared as such in the ivy 
and POM files.

> Avro ivy dependencies include/propagate too many JARs
> -----------------------------------------------------
>
>                 Key: AVRO-348
>                 URL: https://issues.apache.org/jira/browse/AVRO-348
>             Project: Avro
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.2.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> I've been tracking down why my RPM build is failing due to an unexpected 
> ant-1.6.5 JAR file, amongst others; the root cause appears to be avro is 
> over-declaring its dependencies.
> # The dependency on slf4j-simple is causing the problem in hadoop-* projects 
> with >1 SLF4J back end on the classpath.
> # paranamer-ant is pulling in Ant 1.6.5
> # paranamer depends on paranamer-generator and hence qdox, which isn't likely 
> to be needed at run time

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to