[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624224#comment-13624224
]
Travis Crawford commented on HIVE-4278:
---------------------------------------
Hey [~cwsteinbach] - Hive actually already uses maven-ant-tasks for publishing
to maven repos, which is why we use it for publishing to the local repo.
Looking at the
[maven-publish-artifact|http://svn.apache.org/repos/asf/hive/trunk/build.xml]
task we see the maven-ant-tasks used, with options to publish local or a remote
repo (this section could actually be simplified a bit - see
[hcatalog/build-support/ant/deploy.xml|http://svn.apache.org/repos/asf/hive/trunk/hcatalog/build-support/ant/deploy.xml]).
I'm happy to use Ivy to use
[ivy:publish|http://ant.apache.org/ivy/history/2.2.0/use/publish.html] when
installing into the local maven cache, for since we already need
maven-ant-tasks for deploying remotely and they work well, I decided to use
them when installing locally too. When interacting with maven repos I think the
maven-ant-tasks are the way to go, even if Ivy is used for dependency
resolution.
I'll file a followup jira about being consistent with which tool we use to
manage dependencies, but I think that's separate from this issue.
> 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
