[
https://issues.apache.org/jira/browse/AVRO-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846234#comment-13846234
]
Tom White commented on AVRO-1410:
---------------------------------
The patch simply moves the version numbers into the top-level Java POM's
dependency management section (where other version numbers are already
defined), rather than having them defined in the avro-mapred POM. The
dependencies and version numbers for each profile (Hadoop 1 and 2) are
unchanged. So I'm +1 on the change.
I verified that running the tests under each profile was successful with the
change:
{noformat}
mvn clean install
mvn -Dhadoop.version=2 clean install
{noformat}
> 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
(v6.1.4#6159)
