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

Hadoop QA commented on HBASE-11542:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12656805/hbase_11542-v2.patch
  against trunk revision .
  ATTACHMENT ID: 12656805

    {color:red}-1 @author{color}.  The patch appears to contain 9 @author tags 
which the Hadoop community has agreed to not allow in code contributions.

    {color:green}+1 tests included{color}.  The patch appears to include 41 new 
or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10129//console

This message is automatically generated.

> Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
> ----------------------------------------------------------------
>
>                 Key: HBASE-11542
>                 URL: https://issues.apache.org/jira/browse/HBASE-11542
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, test
>    Affects Versions: 0.99.0
>         Environment: RHEL 6.3 ,IBM JDK 6
>            Reporter: LinseyPang
>            Priority: Minor
>             Fix For: 2.0.0
>
>         Attachments: HBASE_11542-1.patch, hbase_11542-v2.patch
>
>
> In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
> leverages the following sun classes:
>    import sun.security.x509.AlgorithmId;
>    import sun.security.x509.CertificateAlgorithmId;
>   ....
> this cause hbase compiler failure if using IBM JDK,  
> There are similar classes like below in IBM jdk: 
> import com.ibm.security.x509.AlgorithmId;
> import com.ibm.security.x509.CertificateAlgorithmId; 
> This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to