[
https://issues.apache.org/jira/browse/AVRO-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908243#action_12908243
]
Owen O'Malley commented on AVRO-545:
------------------------------------
The problem is the standard one that jars shouldn't recursively depend on each
other. It leads to lots of issues. In particular, if Hadoop changes a method,
it can require a new release of avro to use the two together. This is a classic
anti-pattern for software. You never want projects to recursively depend on
each other.
The fact that your pom file lies about its dependencies makes this obvious. If
you made the correct pom file, it would be impossible to release either Avro or
Hadoop except simultaneously.
> Move mapreduce bindings out of avro jar
> ---------------------------------------
>
> Key: AVRO-545
> URL: https://issues.apache.org/jira/browse/AVRO-545
> Project: Avro
> Issue Type: Sub-task
> Components: java
> Affects Versions: 1.4.0
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 1.4.1
>
> Attachments: avro-545.patch
>
>
> MapReduce should not depend on any jars (eg. avro's main jar) that also
> depend on the MapReduce jar.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
