[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623961#comment-13623961
]
Carl Steinbach commented on HIVE-4278:
--------------------------------------
I'm planning to look at this patch more closely tonight. In the meantime I have
a couple questions:
bq. I looked into this a bit and recommend we publish intermediate artifacts to
the local /.m2/repository during the Hive build (currently /.ivy/local)
Why do this? We're still using Ivy, so shouldn't we use the default Ivy local
directory or respect the value of ivy.default.ivy.user.dir if the user has set
it?
bq. Both Ivy and maven support a "changing revision" and this should be pretty
straightforward.
If both Ivy and Maven support this, and if we're currently using Ivy, why not
stick with Ivy instead of introducing another build system into the mix?
> 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
> Assignee: Travis Crawford
> Priority: Blocker
> Fix For: 0.11.0
>
> Attachments: HIVE-4278.D9981.1.patch
>
>
> 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
