[
https://issues.apache.org/jira/browse/HIVE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637159#comment-13637159
]
Carl Steinbach commented on HIVE-4305:
--------------------------------------
bq. or compare it to Hadoop, which has a LOT more complexity in their build
Owen, please give some concrete examples of things that make Hadoop's build
more complex than Hive's. Also, assuming for a moment that this claim is valid,
do you think this added level of complexity excuses the fact that even the
most basic things are broken? What benefits does the project get from using
Maven if simple things like 'mvn compile' and 'mvn eclipse:eclipse' don't work?
And more to the point, are there any situations where you think that Maven is
not the right tool for the job, and if so, what are they?
I think I would find this proposal a lot more credible if someone demonstrated
that it's possible to fix these issues. Here are the tickets in case anyone is
interested in taking up that challenge:
https://issues.apache.org/jira/browse/HADOOP-9383
https://issues.apache.org/jira/browse/HADOOP-9489
I am particularly interested in seeing whether or not someone can fix a problem
like HADOOP-9383 without resorting to git bisect or related methods.
bq. I propose that we have Travis make a Maven build file for the combined Hive
and HCat systems. Then we can debate the value and issues in the particular
patch and how to move the project forward.
Travis has every right to do spend time doing this if he wants to, and I'm
eager to see the results, but I also hope we all agree this doesn't mean we
have decided to switch to Maven. This patch will be judged using the same
criteria that we apply to every other patch. If it's a net positive for the
project it goes in, otherwise it stays out.
Personally I think it would be more pragmatic to spend time improving the build
that we currently have, but this is a volunteer effort where everyone makes
their own decisions about how they spend their time.
bq. The current state is painful with extremely long builds.
This is a qualitative description of a quantitave value. Why be vague? How long
do you think the build should take to complete. What do you think is
reasonable. Please give me a number, and explain what that includes (i.e. jars
only, jars + javadoc, jars + javadoc + tarballs, etc).
bq. We need to move forward and enable the project to evolve quickly so that
Hive can compete with its many comercial competitors.
I have yet to encounter a single Hive user who thinks switching to Maven is
critical for the success of the project. I also think that general code quality
issues have a much bigger impact on developer productivity than anything
related to the build system, but that's just my opinion.
> 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
