| Summary: | Patch dojavadoc so that it can install multiple Javadoc trees | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jean-Noël Rivasseau (RETIRED) <elvanor> |
| Component: | Eclasses | Assignee: | Java team <java> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | alonbl, fordfrog, gentoo |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Need this too. Multi-jar packages can have multiple module-info.java files, one per each jar file, leading to "duplicate class" conflicts. it might be probably better to create a separate package for the extra javadoc. with multijar packages, the way to go is probably to use --module-source-path argument. it is described in this link: https://www.logicbig.com/tutorials/core-java-tutorial/modules/modes.html though it mentions javac, the same option also exist for javadoc command. what i didn't test is whether it generates just one tree combined from multiple modules. |
In the groovy package for instance there are 3 javadoc trees (one for the GDK, one regular for the Groovy API, and the last one is not really clear to me). Currently however only one tree can be installed. The main question is: where should the different trees be installed? Normally javadocs always go to /usr/share/doc/${PF}/html. If several ones are to be installed, what directories should we use? Will it have an impact on tools that may be using the standard location (eg, IDEs for instances, although I don't know if currently any tools take advantage of Gentoo installed javadocs).