[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624153#comment-13624153
]
Carl Steinbach commented on HIVE-4278:
--------------------------------------
bq. Hive already has support for fetching artifacts from Maven repos, and with
a relatively minor change we can publish Hive jars to the local maven repo,
which makes the artifacts available to both dependency resolution tools.
This sounds like a good change to make, but I'm having a hard time
understanding why we would want to use maven-ant-tasks to do this when Ivy
already provides the same functionality.
bq. Once we determine ivy/maven-ant-tasks as the tool we want both project to
use I think we should open a jira to track the transition.
What are the advantages of using maven-ant-tasks in place of Ivy?
> 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
