[
https://issues.apache.org/jira/browse/HIVE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637405#comment-13637405
]
Owen O'Malley commented on HIVE-4305:
-------------------------------------
{quote}
Owen, please give some concrete examples of things that make Hadoop's build
more complex than Hive's.
{quote}
* It contains native executables.
* It contains native libraries.
* It contains jni libraries.
{quote}
I think it would be more pragmatic to spend time improving the build that we
currently have
{quote}
Moving to Maven would be making it better in the opinion of the majority of the
development community. The current Hive build is a complex mess and Ivy and
maven ant tasks is really hard to debug.
Certainly, I believe it is possible to make things worse with Maven. I'm not a
fan of how the Hadoop mavenization was done and I deeply regret not taking the
time to make it better as it went in, but it was still better than the ant +
ivy + maven ant tasks that we had. If it hadn't been, it would have been
rejected. That said, in my experience most projects are better off with Maven
builds than ant + ivy + maven ant tasks.
> 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
> 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: http://www.atlassian.com/software/jira
