[ 
https://issues.apache.org/jira/browse/TEZ-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278089#comment-16278089
 ] 

TezQA commented on TEZ-3873:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12900609/TEZ-3873.001.patch
  against master revision cfede26.

    {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:red}-1 core tests{color}.  The patch failed these unit tests in :
                   
org.apache.tez.runtime.library.common.shuffle.TestShuffleUtils
                  org.apache.tez.mapreduce.output.TestMROutputLegacy
                  org.apache.tez.mapreduce.output.TestMROutput
                  org.apache.tez.mapreduce.output.TestMultiMROutput
                  org.apache.hadoop.mapred.split.TestGroupedSplits
                  org.apache.tez.test.TestTaskErrorsUsingLocalMode
                  org.apache.tez.test.TestExceptionPropagation
                  org.apache.tez.test.TestLocalMode
                  org.apache.tez.client.TestTezClientUtils
                  org.apache.tez.client.TestTezClient
                  org.apache.tez.auxservices.TestShuffleHandler
                  org.apache.tez.tests.TestExtServicesWithLocalMode

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/2696//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2696//console

This message is automatically generated.

> A simple missing dependency error in pom.xml
> --------------------------------------------
>
>                 Key: TEZ-3873
>                 URL: https://issues.apache.org/jira/browse/TEZ-3873
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jinjiang Ling
>            Priority: Minor
>         Attachments: TEZ-3873.001.patch
>
>
> When I use "mvn dependency:tree" to analyze the dependencies of tez, I find 
> there is alway a warning message like these:
> {quote}
> .....
> \[INFO\] 
> ------------------------------------------------------------------------
> \[INFO\] Building Tez 0.9.1-SNAPSHOT
> \[INFO\] 
> ------------------------------------------------------------------------
> \[WARNING\] The POM for org.apache.maven.plugins:maven-enforce-plugin:jar:1.4 
> is missing, no dependency information available
> \[WARNING\] Failed to retrieve plugin descriptor for 
> org.apache.maven.plugins:maven-enforce-plugin:1.4: Plugin 
> org.apache.maven.plugins:maven-enforce-plugin:1.4 or one of its dependencies 
> could not be resolved: Failure to find 
> org.apache.maven.plugins:maven-enforce-plugin:jar:1.4 in 
> http://nexus.server:8081/nexus/content/groups/public/ was cached in the local 
> repository, resolution will not be reattempted until the update interval of 
> proxy.repository has elapsed or updates are forced
> \[INFO\] 
> \[INFO\] --- maven-dependency-plugin:2.8:tree (default-cli) @ tez-docs ---
> .....
> {quote}
> This is caused by a simple mistake of pluginManagement in the pom.xml
> {code:xml}
> <pluginManagement>
>   <plugins>
>     ...
>     <plugin>
>       <groupId>org.apache.maven.plugins</groupId>
>       <artifactId>maven-enforce-plugin</artifactId>
>       <version>1.4</version>
>     </plugin>
>     ......
>   </plugins>
> </pluginManagement>
> {code}
> The correct one should be "maven-{color:red}enforcer{color}-plugin".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to