[
https://issues.apache.org/jira/browse/HIVE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624278#comment-13624278
]
Carl Steinbach commented on HIVE-4305:
--------------------------------------
bq. The main advantage is you write a standard POM, which can use the Apache
parent pom to setup repositories, license, etc.
Ivy's makepom task allows you specify a template POM file that defines the
structure of the generated POM. Couldn't we put the parent pom, repository
setup, license, etc, etc in this template? More info here:
http://ant.apache.org/ivy/history/trunk/use/makepom.html
bq. You also can specify repositories that will be inherited by consumers,
which we need for the datanucleus and sqlline dependencies.
It looks like this is probably covered by the template approach. Please correct
me if I'm wrong. I also wanted to add that since HS2 got committed Hive no
longer depends on sqlline. We should remove this dependency from jdbc/ivy.xml
bq. The feeling I'm getting though is Hive folks like what's already there and
would prefer HCatalog adopt Ivy.
It's not that I like Ivy, it's just that I don't think any of the alternatives
will be any better.
> 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
