On 2017-05-05 17:52, Erik Joelsson wrote:
What's the reason for adding the conditional around SetupCopyFiles in
Javadoc.gmk? The SetupCopyFiles macro should be safe to call with an
empty FILES list. It should evaluate to basically nothing in that case.
I don't think there's an explicit reason
On 2017-05-06 02:22, Brad R. Wetmore wrote:
I applied the patch to the jdk workspace and verified that all of the
instances were updated to
{@docRoot}/../specs/security/standard-names.html, and that no links
remain to the old StandardNames.html.
Sean wrote:
> General: change the text of all
Nah, it's fine.
/Erik
On 2017-05-09 04:37, Magnus Ihse Bursie wrote:
On 2017-05-05 17:52, Erik Joelsson wrote:
What's the reason for adding the conditional around SetupCopyFiles in
Javadoc.gmk? The SetupCopyFiles macro should be safe to call with an
empty FILES list. It should evaluate to b
Can you add similar wording to that effect in DrbgParameters.java?
I'm sorry, that instruction is too unclear for me. :-( The main purpose
of this patch is to prepare for the markdown based specification, not
fixing the entire content. I'll leave modification of the actual
documentation to the
> On May 9, 2017, at 4:23 PM, Brent Christian
>
> I've removed the test case for automatic modules, and added a @run action for
> each policy file + system classloader configuration. I also removed the code
> to compile test sources, using @build instead.
>
> I also made some (hopefully) cla
