[
https://issues.apache.org/jira/browse/HIVE-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13253643#comment-13253643
]
Andrew Bayer commented on HIVE-2646:
------------------------------------
...but make sure to nuke your ~/.ivy2/cache/org.apache.hive before rebuilding,
or you'll end up with stale Ivy artifacts pointing to commons-codec 1.3.
> Hive Ivy dependencies on Hadoop should depend on jars directly, not tarballs
> ----------------------------------------------------------------------------
>
> Key: HIVE-2646
> URL: https://issues.apache.org/jira/browse/HIVE-2646
> Project: Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Affects Versions: 0.8.0
> Reporter: Andrew Bayer
> Assignee: Andrew Bayer
> Priority: Critical
> Fix For: 0.9.0
>
> Attachments: HIVE-2646.D2133.1.patch, HIVE-2646.D2133.10.patch,
> HIVE-2646.D2133.11.patch, HIVE-2646.D2133.12.patch, HIVE-2646.D2133.13.patch,
> HIVE-2646.D2133.14.patch, HIVE-2646.D2133.15.patch, HIVE-2646.D2133.2.patch,
> HIVE-2646.D2133.3.patch, HIVE-2646.D2133.4.patch, HIVE-2646.D2133.5.patch,
> HIVE-2646.D2133.6.patch, HIVE-2646.D2133.7.patch, HIVE-2646.D2133.8.patch,
> HIVE-2646.D2133.9.patch, HIVE-2646.diff.txt
>
>
> The current Hive Ivy dependency logic for its Hadoop dependencies is
> problematic - depending on the tarball and extracting the jars from there,
> rather than depending on the jars directly. It'd be great if this was fixed
> to actually have the jar dependencies defined directly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
