[
https://issues.apache.org/jira/browse/TEZ-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624315#comment-14624315
]
TezQA commented on TEZ-2616:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12744989/TEZ-2616.001.patch
against master revision cb59851.
{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 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) 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-TEZ-Build/895//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/895//console
This message is automatically generated.
> Fix build warning by undefined version of maven-findbugs-plugin
> ---------------------------------------------------------------
>
> Key: TEZ-2616
> URL: https://issues.apache.org/jira/browse/TEZ-2616
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Tsuyoshi Ozawa
> Assignee: Tsuyoshi Ozawa
> Attachments: TEZ-2616.001.patch
>
>
> {quote}
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.tez:tez-api:jar:0.8.0-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.codehaus.mojo:findbugs-maven-plugin is missing. @
> org.apache.tez:tez:0.8.0-SNAPSHOT, /home/ubuntu/tezdev/pom.xml, line 1148,
> column 15
> {quote}
> This problem is caused since the plugin is used not only in build section,
> but also reporting section. The usage is same as maven-javadoc-plugin, so
> similar issue can happen for maven-javadoc-plugin. This JIRA suggests we add
> new properties findbugs-maven-plugin.version and javadoc-maven-plugin.version
> for avoiding similar issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)