[
https://issues.apache.org/jira/browse/HIVE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625693#comment-13625693
]
Travis Crawford commented on HIVE-4305:
---------------------------------------
Unless there are objections, I think we should convert HCatalog back to ivy for
managing its dependencies. Reason being Hive already uses it and we're
integrating HCatalog into Hive, so unless there's a strong reason not to we
should do things the "hive way". I'd very much like to avoid any path that
involves major changes to stuff that already works.
maven-ant-tasks vs. ivy are basically the same. I happen to prefer the former
but they're basically equivalent.
Thoughts?
> Use a single system for dependency resolution
> ---------------------------------------------
>
> Key: HIVE-4305
> URL: https://issues.apache.org/jira/browse/HIVE-4305
> Project: Hive
> Issue Type: Improvement
> Components: Build Infrastructure, HCatalog
> Reporter: Travis Crawford
>
> Both Hive and HCatalog use ant as their build tool. However, Hive uses ivy
> for dependency resolution while HCatalog uses maven-ant-tasks. With the
> project merge we should converge on a single tool for dependency resolution.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
