Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 94E0BD859 for ; Tue, 9 Oct 2012 01:38:03 +0000 (UTC) Received: (qmail 50064 invoked by uid 500); 9 Oct 2012 01:38:03 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 49983 invoked by uid 500); 9 Oct 2012 01:38:03 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 49849 invoked by uid 99); 9 Oct 2012 01:38:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Oct 2012 01:38:03 +0000 Date: Tue, 9 Oct 2012 01:38:03 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@hbase.apache.org Message-ID: <2016447593.12220.1349746683238.JavaMail.jiratomcat@arcas> In-Reply-To: <867484045.11661.1349742122945.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HBASE-6961) In place scripts fail if mvn install hasn't been run MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-6961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472051#comment-13472051 ] Hadoop QA commented on HBASE-6961: ---------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12548338/HBASE-6961-0.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 hadoop2.0{color}. The patch compiles against the hadoop 2.0 profile. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 81 warning messages. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 findbugs{color}. The patch appears to introduce 5 new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/3019//console This message is automatically generated. > In place scripts fail if mvn install hasn't been run > ---------------------------------------------------- > > Key: HBASE-6961 > URL: https://issues.apache.org/jira/browse/HBASE-6961 > Project: HBase > Issue Type: Bug > Reporter: Elliott Clark > Assignee: Elliott Clark > Attachments: HBASE-6961-0.patch > > > bin/hbase tries to get dependencies of the project however it fails if mvn install hasn't already satisfied hbase-hadoop-compat test-jar. -- 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