[
https://issues.apache.org/jira/browse/HBASE-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111565#comment-14111565
]
Hadoop QA commented on HBASE-11832:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12664494/HBASE-11832.patch
against trunk revision .
ATTACHMENT ID: 12664494
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestHRegion
org.apache.hadoop.hbase.TestRegionRebalancing
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/10598//console
This message is automatically generated.
> maven release plugin overrides command line arguments
> -----------------------------------------------------
>
> Key: HBASE-11832
> URL: https://issues.apache.org/jira/browse/HBASE-11832
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.4
> Reporter: Enoch Hsu
> Assignee: Enoch Hsu
> Priority: Minor
> Fix For: 0.99.0
>
> Attachments: HBASE-11832.patch
>
>
> Inside the pom under the maven-release-plugin there is a configuration that
> defines what the release-plugin uses like so
> <configuration>
> <!--You need this profile. It'll sign your artifacts.
> I'm not sure if this config. actually works though.
> I've been specifying -Papache-release on the command-line
> -->
> <releaseProfiles>apache-release</releaseProfiles>
> <!--This stops our running tests for each stage of maven release.
> But it builds the test jar. From SUREFIRE-172.
> -->
> <arguments>-Dmaven.test.skip.exec</arguments>
> <pomFileName>pom.xml</pomFileName>
> </configuration>
> The arguments are hardcoded in and will automatically override any arguments
> the user passes in from the command line.
> I propose to modify this to the following
> <arguments>-Dmaven.test.skip.exec ${arguments}</arguments>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
