[ https://issues.apache.org/jira/browse/AVRO-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845517#comment-13845517 ]
Tom White commented on AVRO-1410: --------------------------------- You can build against different versions of Hadoop by specifying {{-Dhadoop1.version=...}} for Hadoop 1, or {{-Dhadoop.version=2 -Dhadoop2.version=...}} for Hadoop 2. Also, Hadoop is a provided (or test) dependency for avro-mapred so you can use a different version of Hadoop at runtime, as long as it is the same major version (1 or 2). > 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)