[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624270#comment-13624270
]
Carl Steinbach commented on HIVE-4278:
--------------------------------------
The ivy:publish task allows you publish to either a local or remote repository.
Here's a page on the Apache website that describes how to publish release
artifacts to Apache's Nexus Pro repository using Ant+Ivy:
http://www.apache.org/dev/publishing-maven-artifacts.html#ant
bq. 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.
What do you need to special-case?
bq. 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?
The small change that's been proposed is a hack that won't make any sense to
someone who encounters it six months from now. Hive uses Ivy, so why should it
publish artifacts to the local Maven repository?
> 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
