Major Description
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.