[
https://issues.apache.org/jira/browse/HADOOP-11470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270240#comment-14270240
]
Hadoop QA commented on HADOOP-11470:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12690929/HADOOP-11470.001.patch
against trunk revision cc2a745.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestDecommission
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5383//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5383//console
This message is automatically generated.
> Remove some uses of obsolete guava APIs from the hadoop codebase
> ----------------------------------------------------------------
>
> Key: HADOOP-11470
> URL: https://issues.apache.org/jira/browse/HADOOP-11470
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Attachments: HADOOP-11470.001.patch
>
>
> Along the same vein as HADOOP-11286, there are now several remaining usages
> of guava APIs that are now incompatible with a more recent version (e.g. 16).
> This JIRA proposes eliminating those usages. With this, the hadoop code base
> should run/compile cleanly even if guava 16 is used for example.
> This JIRA doesn't propose upgrading the guava dependency version however
> (just making the codebase compatible with guava 16+).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
