[ 
https://issues.apache.org/jira/browse/HCATALOG-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13458133#comment-13458133
 ] 

Travis Crawford commented on HCATALOG-502:
------------------------------------------

Hey [~avandana] - can you trash the cached Hive artifacts and try again. 
Something along the lines of:

{code}
rm -rf ~/.ivy2/cache/org.apache.hive/
rm -rf ~/.ivy2/local
rm -rf ~/.m2/repository/org/apache/hive
{code}

I believe what's happened here is you have a stale cache of hive 
0.10.0-SNAPSHOT jars, and when you build you're not finding a recently added 
symbol. Those two lines were added to fix HCATALOG-498. Trashing your caches 
should cause you to download the latest snapshots, which have these symbols.
                
> HCatalog dependency resolution fails due to missing repo
> --------------------------------------------------------
>
>                 Key: HCATALOG-502
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-502
>             Project: HCatalog
>          Issue Type: Bug
>            Reporter: Travis Crawford
>            Assignee: Travis Crawford
>         Attachments: HCATALOG-502_bad_repo.1.patch
>
>
> Recently some HCatalog subprojects have been switched to 
> [maven-ant-tasks|http://maven.apache.org/ant-tasks/index.html] for dependency 
> management, away from Ivy. Maven has a mechanism for dependencies to update 
> the list of repositories used for dependency resolution, and one of these 
> transitive repos has moved and is causing issues.
> This issue can be reproduced by removing the following and doing a clean 
> build.
> {code}
> rm -rf ~/.m2/repository/asm
> {code}
> We can fix this issue by disabling the misconfigured repo. Maven is a complex 
> tool and I looked for how to disable transitive repos entirely, but was not 
> able to figure that out. If someone knows how to disable transitive repos 
> entirely I would be interested to try that instead.

--
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

Reply via email to