that works because OpenJDK uses module-source-path, i.e.
src/<modulename>/<*.java>
Maven uses source-path because it matches exactly one module , i.e.
src/main/java/<*.java>
Aggregator for modules requires to make use of module-source-paths.
I guess we need to consider to make use of symbolic links :(
thanks,
Robert
On Sat, 18 Nov 2017 17:44:23 +0100, Hervé BOUTEMY <[email protected]>
wrote:
JDK javadoc seems to cover the "aggregated javadocs" scenario: in Java 9
terms, that's "multi-modules" = exactly the case for JDK 9 javadoc [1]
I don't know what's the command line to produce this, but looks feasible
from
javadoc side
Regards,
Hervé
[1] https://docs.oracle.com/javase/9/docs/api/overview-summary.html
Le samedi 18 novembre 2017, 17:38:23 CET Hervé BOUTEMY a écrit :
Le samedi 18 novembre 2017, 17:18:06 CET Mark Raynsford a écrit :
> On 2017-11-18T16:14:04 +0000
>
> Mark Raynsford <[email protected]> wrote:
> > Presumably, with the module-info.java files
> > excluded, it reverts back to plain classpath style JavaDoc.
>
> Actually, it results in sort of weird looking JavaDoc that only
> contains a single module, and claims that all packages are in
>
> that module:
> http://outland.iw.int.arc7.info/2017/11/18/apidocs/index.html
>
> That behaviour seems like it might be a bug in the actual JavaDoc tool
> itself.
IIUC, javadoc does not cover aggregated javadocs scenario?
I would not call that a bug, but a missing feature :)
Regards,
Hervé
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
