I've been using the src.zip that comes with the JDK install on my mac. In
general, I'm going to be applying this process to arbitrary source jars for
various maven dependencies and so i'm just trying to work out how all the
parameters now work in a modularized world. I'll play with what you've
sh
Justin,
Thanks for the extra info.
There is one improvement coming soon for --module-source-path.
The current spec embodies an assumption about the naming of directories
contain source code. This may not hold for some existing projects that
may be converted to use modules. The improvement w
Justin,
It seems there are two forms of src.zip out in the wild. My previous
response was based on using a src.zip that is essentially just a zip of
the contents of appropriate OpenJDK repo. As such, it has top level
directories like "make", "src", "test", and the src/ directory does not
co
Justin,
To follow up on this some more, can you tell me where you are getting
"the java9 src.zip" that you refer to?
Or, if you can't recall, can you check the layout of the contents?
Is it like this:
openjdk/ADDITIONAL_LICENSE_INFO
openjdk/ASSEMBLY_EXCEPTION
openjdk/bin
openjdk/c
Justin,
This ought to be simple, but as you discovered, it isn't.
I tried to generate the docs using the JDK 10 src.zip, available here:
https://download.java.net/openjdk/jdk10/ri/openjdk-10_src.zip
After ou unzip the sources, the command ought to be as simple as
something like the following:
I'm trying to run javadoc against the java9 src.zip and I have no idea how
to handle the modules. Even if I go with the classic "javadoc @sources"
approach I get an error about too many modules defined. I've tried a
number of variations but I can't quite seem to crack that nut.
My latest attempt
