hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11422) Specification of scope is missing for certain Hadoop dependencies
Date Tue, 01 Jul 2014 06:18:24 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048564#comment-14048564

stack commented on HBASE-11422:

Did the first patch have classifiers in it?  Classifying hasn't worked consistently across
mvn phases in my experience.

Patch looks good.  If I were testing, I'd be looking at the tgz assembly making sure it had
hadoop jars all of same version (I'm pretty sure I've looked at this in the past and IIRC
it used to work properly only putting hadoop versions of a particular type into assembly...
but hey... stuff changes).  Would also try publishing a snapshot to make sure all went up
to the repo w/ correct references.  I can try it if you just say the word [~cos], np.

On hbase-testing-util, let me look over at the other issue you raise. I'm not sure I grok
its need myself (the original hbase-downstreamer seems to be able to use testing utils w/o
need of hbase-testing-util but I must be missing something...)

> Specification of scope is missing for certain Hadoop dependencies
> -----------------------------------------------------------------
>                 Key: HBASE-11422
>                 URL: https://issues.apache.org/jira/browse/HBASE-11422
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Konstantin Boudnik
>             Fix For: 0.99.0, 0.98.4
>         Attachments: HBASE-11422.0.98.patch
> [~cos] reported in the mailing thread, 'HBase 0.98.x dependency problems', that specifying
hadoop-two.version with value other than 2.2.0 pulls in incorrect dependencies such as:
> {code}
> [INFO] |  \- org.apache.hadoop:hadoop-hdfs:test-jar:tests:2.2.0:compile
> {code}
> This is due to missing specification of scope in the pom.xml files.

This message was sent by Atlassian JIRA

View raw message