Hi!
There is an interesting question up on StackOverflow, "How does the
Javadoc deal with the visibility of modules in Java 9?".
http://stackoverflow.com/q/41929425/2525313
It asks whether there will be an easy way to generate documentation
based on accessibility?
Next to an actual ans
Nicolai,
The simple answer is "Yes, there will be an easy way to generate
documentation based on accessibility",
and "yes, the javadoc tool is module aware".
We've added new options that generalize the existing simple options, so
that you can have detailed
control if you really need it, but t
I see the command line help text has not been updated for the existing
simple options. That is a bug.
-- Jon
On 01/30/2017 04:05 PM, Jonathan Gibbons wrote:
Nicolai,
The simple answer is "Yes, there will be an easy way to generate
documentation based on accessibility",
and "yes, the javad
Hi Jonathan,
On 31/01/17 00:05, Jonathan Gibbons wrote:
> From the command-line help, the relevant new options are the following:
> . . .
> The good news is that you can use the existing simple options, which are
> now
> internally defined in terms of those new options
>
> -public
>
Sorry, cut and paste error; the second occurrence should have been -private.
-public
--show-module-contents api --show-packages exported
--show-types public --show-members public
-protected (the long-standing default)
--show-module-contents api --show-packages ex
