[
https://issues.apache.org/jira/browse/HIVE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624258#comment-13624258
]
Travis Crawford commented on HIVE-4305:
---------------------------------------
The main advantage is you write a standard POM, which can use the Apache parent
pom to setup repositories, license, etc. You also can specify repositories that
will be inherited by consumers, which we need for the datanucleus and sqlline
dependencies. By using maven-ant-tasks the pom you publish in the central repo
can be better than the one generated by ivy.
The feeling I'm getting though is Hive folks like what's already there and
would prefer HCatalog adopt Ivy. I'm fine with that. I'd just like to make sure
everyone is on the same page before doing a bunch of migration work.
> 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
