hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Steinbach (JIRA)" <>
Subject [jira] [Commented] (HIVE-4305) Use a single system for dependency resolution
Date Fri, 19 Apr 2013 00:51:16 GMT


Carl Steinbach commented on HIVE-4305:

Owen, the critical point is that in order to use Maven we have to
completely replace all of the build scripts, and probably write a
bunch of Maven plugins too. Add to that the additional costs of
bringing existing Hive contributors up to speed with the new build
system. This seems like a pretty big cost to incur, which is why I'm
trying to figure out what we expect to get in return. So far the
answer seems to be "nothing that we can't accomplish already with

I anticipate that your response to this will be something along the
lines of "yes, they provide equivalent functionality and features, but
Ant/Ivy is hard to use and Maven just works." So before you say that
I have a simple request to make. Please check out the trunk branch of
the hadoop-common repository, run the command 'mvn compile', and tell
me what happens.

Do you think the Hadoop folks should note this issue in their 4+ page
long BUILDING.txt file, or would you advocate that they remove this
file entirely and deny that it ever existed since it contradicts a
central tenet of Maven dogma, namely that "you can download a Maven
project and build it without reading the build file"?

> Use a single system for dependency resolution
> ---------------------------------------------
>                 Key: HIVE-4305
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Build Infrastructure, HCatalog
>            Reporter: Travis Crawford
>            Assignee: Carl Steinbach
> 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:

View raw message