See http://hbase.apache.org/xref/org/apache/hadoop/hbase/util/JVM.html Demai. It is facade behind which we hide JVM differences. Sounds like we need to add handling of the x509 references.
St.Ack On Thu, Jun 26, 2014 at 11:57 AM, Demai Ni <[email protected]> wrote: > hi, folks, > > a few days ago, jira HBase-10336 added a UT KeyStoreTestUtil.java, which > leverages the following sun classes: > import sun.security.x509.AlgorithmId; > import sun.security.x509.CertificateAlgorithmId; > .... > > well, it happens that I am amongst the minority who are using IBM JDK, and > won't compile/run this class. > There are similar classes like below in IBM jdk: > import com.ibm.security.x509.AlgorithmId; > import com.ibm.security.x509.CertificateAlgorithmId; > > I think a ClassLoader could be a solution here, wondering what's the common > way in HBase for such situation or an example will be much appreciated. > > Basically, so that we can compile/run the UT on both JDK. thanks > > Demai >
