[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624254#comment-13624254
]
Travis Crawford commented on HIVE-4278:
---------------------------------------
Re: why maven-ant-tasks are used at all, I could be mistaken but I don't think
you can publish to a remote maven repo with ivy. This is likely why Hive
already uses maven-ant-tasks. The reason I prefer maven-ant-tasks to ivy when
interacting with local maven repos is because you don't need to special-case
things.
Before redoing the patch, I'd like to reach consensus on what approach to take.
Am I hearing we should completely migrate HCatalog to ivy for its dependencies
now rather than making a small change to where Hive publishes its internal
dependencies?
> 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
