You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2014/07/09 08:26:05 UTC

[jira] [Commented] (BIGTOP-1369) Hive Debian rules file does not set maven.repo.local

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

Roman Shaposhnik commented on BIGTOP-1369:
------------------------------------------

Good catch!

> Hive Debian rules file does not set maven.repo.local
> ----------------------------------------------------
>
>                 Key: BIGTOP-1369
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1369
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Julien Eid
>
> The Hive Debian rules file when calling do-component-build does not set the maven.repo.local command line argument and so when Hive builds it uses the default location for the local maven repo, which breaks if HBase was built in a different m2 repo while Hive was using the default, causing Hive to be unable to find hbase-common.
> Noticied this issue because my HOME variable was not set to /root and was instead /, which caused HBase to put artifacts in /.m2 while Hive was looking for them in /root/.m2.
> You can see https://github.com/apache/bigtop/blob/master/bigtop-packages/src/deb/hbase/rules that -Dmaven.repo.local gets set, but in https://github.com/apache/bigtop/blob/master/bigtop-packages/src/deb/hive/rules it's not.
> I also saw that HCatalog's rules file does not set the variable as well, but I haven't check yet if that breaks things.



--
This message was sent by Atlassian JIRA
(v6.2#6252)