Thanks for that explanation, Jon.
I'm asking these questions because I'm near the end of modularizing a
very old body of software, Apache Derby. I have successfully created
module descriptors for all of the Derby components and I have not had to
rename any directories. The naming limitation yo
Rick,
Thank you for explaining the context of your questions.
With respect, you are mistaken with respect to javac's behavior, if only
because it's the same code shared by javac and javadoc,
--module-source-path requires there to be a level in the directory
hierarchy that is named for the mo
Sorry, I missed that detail when looking at your example yesterday.
The error message says it all.
When you're working with multiple modules on the module source path,
each module must be in a directory that is named after the module it
contains. Think of it as the module-level equivalent of t
Hello Priya,
The specific changes looks ok to me.
As a separate effort, I recommend searching for other accesses in the Doclet
to javax.lang.model through calls in Utils, these need to be investigated.
Note: there maybe legitimate cases where raw members and types are needed,
but for the most pa
Thanks, Jon. That moved the problem forward. Now I am getting an error
because a module's name does not match the root directory of its source
code. The following command...
javadoc --module-source-path ./java \
-d build/javadoc \
--module firstmodule,secondmodule
...raises the
