jira-importer commented on issue #741: URL: https://github.com/apache/maven-javadoc-plugin/issues/741#issuecomment-2957349262
**[Martin Desruisseaux](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=desruisseaux)** commented I think that the issue is deeper than aggregated javadoc only. In order to generate aggregated javadoc with a front page listing modules, we need to use the `\--module-path` and `\--module-source-path` options of JDK tools (if there is another way, I did not found it yet). But those options require a directory having the exact module name. Current Maven standard directory layout is incompatible with this requirement. This problem impacts no only javadoc, but all JDK tools working with modules (at least `javadoc`, `javac` and `jlink`). For example when used with `javac`, "aggregated compilation" allows to run Annotation Processing Tools on all modules in one pass (useful if the processing tools want to combine information from all modules). If we need to revisit directory layout in order to support aggregated javadoc, then we could expand the scope for fixing also other issues (in my opinion) in supporting multi-language projects, for example in projects using Java, Python and C/C++ together. A new directory layout [has been proposed on the Maven developer mailing list](https://mail-archives.apache.org/mod_mbox/maven-dev/201808.mbox/%3C91eb6c15-9fc6-6d2a-56c9-962c2be4c227%40geomatys.com%3E). But [implementing and experimenting](https://github.com/Geomatys/maven-plugins/wiki) it would require volunteer time, maybe outside the current Maven maintainers team, until the value of such proposal is demonstrated (or not). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
