Question around the 8054717 fix

Seán Coffey sean.coffey at
Mon Jun 15 13:30:41 UTC 2015


I had a security library fix reviewed last week [1] and all was ok with 
builds back then. Today, I found that my build is broken and I think 
it's down to the changes introduced from the 8054717 fix.

The build error (snippet) is :

> /opt/jprt/T/P1/081059.scoffey/s/jdk/src/jdk.crypto.pkcs11/share/classes/sun/security/pkcs11/ error: ECPublicKeyImpl(byte[]) is not public in ECPublicKeyImpl; cannot be accessed from outside package
>                  return new ECPublicKeyImpl(x509Spec.getEncoded());
>                         ^
> /opt/jprt/T/P1/081059.scoffey/s/jdk/src/jdk.crypto.pkcs11/share/classes/sun/security/pkcs11/ error: constructor ECPublicKeyImpl in class ECPublicKeyImpl cannot be applied to given types;
>                  return new ECPublicKeyImpl(
>                         ^
>    required: byte[]
>    found: ECPoint,ECParameterSpec
>    reason: actual and formal argument lists differ in length
I've confirmed that I do have the correct access type modifications in 
the ECPublicKeyImpl constructor (moved to public)

The build system appears to be picking up the older ECPublicKeyImpl 
class in the bootstrap JDK and not the newly built classes. 8054717 
appears to have modified bootclasspath settings.

Is this an issue with my security fix or a build issue ? I've tried the 
build on my local system and an JPRT.



More information about the build-dev mailing list