Well, it turns out that I do have to update modules.xml with the
jdk.crypto.ucrypto module info (Thanks to a tip from Mandy). I have sent
the necessary webrev for this to jigsaw alias separately.
Thanks,
Valerie
On 10/15/2014 2:39 PM, Valerie Peng wrote:
The <top>/modules.xml already allows jdk.crypto.ucrypto to access
sun.nio.cs, sun.security.action, sun.security.internal.spec,
sun.security.util packages.
The build completes and no module access errors. So, it seems to me
that current content of modules.xml is fine.
Thanks,
Valerie
On 10/15/2014 11:54 AM, Alan Bateman wrote:
On 15/10/2014 19:46, Valerie Peng wrote:
Hi, build experts,
Could you please review the build-related changes for 8046002: Move
Ucrypto to the open jdk repo?
The rest (src/test) has been reviewed by my peers in security team.
Bug: https://bugs.openjdk.java.net/browse/JDK-8046002
Webrev: http://cr.openjdk.java.net/~valeriep/8046002/webrev.01/
Is there a webrev for the top-level repo? I assume that at least
<top>/modules.xml will need to be updated.
-Alan.
