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

Hadoop QA commented on HADOOP-11838:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12725725/HADOOP-11838-v1.patch
  against trunk revision 1b89a3e.

    {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:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-common-project/hadoop-auth.

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

This message is automatically generated.

> Externalize AuthToken interface
> -------------------------------
>
>                 Key: HADOOP-11838
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11838
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Kai Zheng
>            Assignee: Kai Zheng
>         Attachments: HADOOP-11838-v1.patch
>
>
> This suggests refactoring existing {{AuthToken}} utility class and 
> externalizing a generic {{AuthToken}} API.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to