Mailing-List: contact dev-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@avro.apache.org
Date: Sun, 8 Dec 2013 23:44:06 +0000 (UTC)
From: "E. Sammer (JIRA)" <jira@apache.org>
To: dev@avro.apache.org
Message-ID: <JIRA.12683530.1386544743479.92.1386546246980@arcas>
In-Reply-To: <JIRA.12683530.1386544743479@arcas>
References: <JIRA.12683530.1386544743479@arcas>
Subject: [jira] [Updated] (AVRO-1410) Explicit version specification in pom
 prevents dependency management
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

E. Sammer updated AVRO-1410:
----------------------------

    Status: Patch Available  (was: Open)

> 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.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
(v6.1.4#6159)