[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phabricator updated HIVE-4278:
------------------------------
Attachment: HIVE-4278.D9981.1.patch
travis requested code review of "HIVE-4278 [jira] HCat needs to get current
Hive jars instead of pulling them from maven repo".
Reviewers: JIRA
Update build so HCatalog uses Hive jars from the current build. Currently
HCatalog pulls snapshot jars from the apache snapshots repo.
TEST PLAN
I tested by trashing all Hive/HCatalog artifacts from my local Ivy/Maven
repos, did clean builds, and observed where dependencies are resolved from.
During the build Hive submodules use artifacts from the current build (ivy
recognizes artifacts from current build that have been published to the local
maven repo). HCatalog also uses the local snapshots.
REVISION DETAIL
https://reviews.facebook.net/D9981
AFFECTED FILES
build-common.xml
build-support/ant/dependencies.xml
build.properties
build.xml
builtins/build.xml
hcatalog/pom.xml
ivy/common-configurations.xml
ivy/ivysettings.xml
ql/build.xml
service/ivy.xml
MANAGE HERALD RULES
https://reviews.facebook.net/herald/view/differential/
WHY DID I GET THIS EMAIL?
https://reviews.facebook.net/herald/transcript/23865/
To: JIRA, travis
> 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
