[
https://issues.apache.org/jira/browse/HIVE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636112#comment-13636112
]
Carl Steinbach commented on HIVE-4305:
--------------------------------------
GUYS! Turns out before you can run 'mvn eclipse:eclipse' from the root
directory you first have to cd into the hadoop-maven-plugins directory
and run 'mvn install' from there. Then you cd back up a level
and run 'mvn eclipse:eclipse' and it JUST WORKS! After that I imported
all of this stuff into eclipse and that JUST WORKED too! Convention
over configuration for the win! Please forgive me for being such a n00b
earlier. Some of these conventions just take a bit of time to pick up.
The thing that sucks the most about using Maven is that it makes you forget
how broken everything else is. Like after I finished importing the code
(thanks Maven!) eclipse is now complaining about 2,501 errors and a bunch
of unsatisfied dependencies on classes in the oah.ipc.protobuf namespace.
I think that last part is a good clue that it's an eclipse bug because maven
invented dependency management and everyone knows it just works!
> 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
