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: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | alonbl, fordfrog, gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jean-Noël Rivasseau (RETIRED)
![]() 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 reply to Miroslav Šulc from comment #3) > [...] > 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. this is proven to work for ejavac and ejavadoc with dev-java/cdi-api: 4.0.1-r3 from https://github.com/gentoo/gentoo/pull/35305. closing this as wontfix |