avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1410) Explicit version specification in pom prevents dependency management
Date Mon, 09 Dec 2013 19:26:07 GMT

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

Doug Cutting commented on AVRO-1410:

We build different versions of the Avro mapred jar for different versions of Hadoop (where
abstract classes changed to interfaces).  See AVRO-1170.  Unit tests do not check this.  Are
you certain your patch does not break this?

> Explicit version specification in pom prevents dependency management
> --------------------------------------------------------------------
>                 Key: AVRO-1410
>                 URL: https://issues.apache.org/jira/browse/AVRO-1410
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.7.5
>            Reporter: E. Sammer
>            Assignee: E. Sammer
>             Fix For: 1.7.6
>         Attachments: AVRO-1410-2.patch, AVRO-1410.patch
> While building Avro against different versions of Hadoop I found that avro-mapred explicitly
specifies the versions of some of the Hadoop dependencies rather than deferring to its own
dependency management. This makes it impossible to build against other versions of Hadoop
without pom-hackery. It's also a potential maintenance issue for Avro in that changes to the
dependency management section of the Java top level pom won't be picked up by the mapred module.

This message was sent by Atlassian JIRA

View raw message