[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13621524#comment-13621524
]
Travis Crawford commented on HIVE-4278:
---------------------------------------
I looked into this a bit and recommend we publish intermediate artifacts to the
local {{~/.m2/repository}} during the Hive build (currently {{~/.ivy/local}}),
and configure all submodules to use the local maven repo first when resolving
artifacts. Both Ivy and maven support a "changing revision" and this should be
pretty straightforward.
Details about Ivy support of changing revisions:
http://ant.apache.org/ivy/history/latest-milestone/concept.html#change
Long-term, I think we should consider using a single resolver for all
dependencies. When incubating, I migrated HCatalog from ivy to the maven ant
tasks and have been very happy with them. If folks are comfortable with this
I'd be interested in migrating Hive entirely to the maven ant tasks. However,
if folks want to stick with Ivy I think we should switch HCatalog back to Ivy
too for consistency.
> HCat needs to get current Hive jars instead of pulling them from maven repo
> ---------------------------------------------------------------------------
>
> Key: HIVE-4278
> URL: https://issues.apache.org/jira/browse/HIVE-4278
> Project: Hive
> Issue Type: Sub-task
> Components: Build Infrastructure, HCatalog
> Affects Versions: 0.11.0
> Reporter: Alan Gates
> Priority: Blocker
> Fix For: 0.11.0
>
>
> The HCatalog build is currently pulling Hive jars from the maven repo instead
> of using the ones built as part of the current build. Now that it is part of
> Hive it should use the jars being built instead of pulling them from maven.
--
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
