You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/09/18 12:10:53 UTC
[jira] [Commented] (HBASE-9571) hbase-client does not depend on map
reduce, but the pom.xml includes it
[ https://issues.apache.org/jira/browse/HBASE-9571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770630#comment-13770630 ]
Hadoop QA commented on HBASE-9571:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12603780/9571.v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop 1.0 profile.
{color:red}-1 hadoop2.0{color}. The patch failed to compile against the hadoop 2.0 profile.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/7292//console
This message is automatically generated.
> hbase-client does not depend on map reduce, but the pom.xml includes it
> -----------------------------------------------------------------------
>
> Key: HBASE-9571
> URL: https://issues.apache.org/jira/browse/HBASE-9571
> Project: HBase
> Issue Type: Bug
> Components: build, Client
> Affects Versions: 0.98.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Priority: Minor
> Fix For: 0.96.1
>
> Attachments: 9571.v1.patch
>
>
> mvn dependency:analyze is strange on this one. You can remove or add the dependency, it won't complain about "used but undeclared" or "undeclared but used" dependencies. But it does a difference in dependency:tree or for the client application.
--
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