[
https://issues.apache.org/jira/browse/AVRO-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908377#action_12908377
]
Owen O'Malley commented on AVRO-545:
------------------------------------
This is a regression. The 1.4.0 pom does not accurately reflect the
dependencies. That is broken. Users should be able to depend on your pom and
automatically get the transitive dependencies. Clearly, if you weren't breaking
the rules by introducing a cycle in the dependency graph you *would* include
the Hadoop jars in your pom.
I also noticed that your avro-tool jar includes everything from the build
classes, which includes everything from the main avro jar. I assume that is
unintentional.
If you are really going to ignore my patch and not fix this until the end of
the year. I'll need to fork Avro back into Hadoop and I'd really rather avoid
that. I already have more than enough work cleaning up Hadoop.
> 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.
