[
https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078802#comment-14078802
]
stack commented on HBASE-11542:
-------------------------------
[~Linsey] Factory seems fine. You looked at the JVM class and it too hard to
coral JVM vendor stuff inside there? What did you think of the
[[email protected]] notion above of "Instead of programmatically
creating a keystore containing a self-signed certificate and keypair, perhaps
we can generate one once by hand, stringify it, and just use that...."? Thanks.
> 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, hbase11542-0.99-v3.patch,
> hbase11542-0.99-v3.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)
