Hi Jon,
that's what I've tried to do, but when using Marks project as example it
fails with:
[parsing completed 0ms]
[loading /modules/java.base/module-info.class]
Loading source files for package com.io7m.bugs.c...
javadoc: error - No source files for package com.io7m.bugs.c
1 error
I'm kin
'Ello.
Thanks for the detailed response!
On 2017-11-19T10:50:08 -0800
Jonathan Gibbons wrote:
>
> There is one other solution ... but it comes more in the "advanced"
> category, but may be reasonable in the context of the Maven plugin.
> You can use
> --patch-module /module-name/=/path/
>
Robert,
For javac and javadoc, --patch-module is also permitted for sources; it
was a late change/addition towards the end of JDK 9.
In the test case you are playing with, is com.io7m.bugs.c a package name
as well as a module name? If not, and if you think javadoc is
misinterpreting the nam
If you are wanting to generate javadoc for multiple modules, you have
two possibilities ...
From the command line ...
Yes, you must use --module-source-path, but it allows a syntax for cases
like this.
It does require that the source for each module must be "under" a
directory with the same n
Hello.
We're in the process of trying to get the maven-javadoc-plugin to work
correctly when generating documentation for modules. I have a simple
test case here that fails:
https://github.com/io7m/maven-javadoc-bug-20171118
See the README.txt for the full build log and error messages.
I thin
