Notes about issue random_order_in_documentation_generated_by_javadoc in experimental
| Identifier: | random_order_in_documentation_generated_by_javadoc |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| Description: |
Some entries inside individual "class-use" documentation pages are emitted in different orders. This appears to only happen with multi-module maven projects, i.e. possibly during `mvn javadoc:aggregate`. . In `jacoco`, you can observe files are generated consistently in the individual submodule documentation folders, but then differently when aggregated. Maybe a coincidence. . Historically, there were some other issues. These have disappeared, but it's not clear why. The major version of OpenJDK has changed since these issues were reported (was 7, now 8), although the code that was believed to be at fault remains unchanged. These are detailed below. . The `package-tree.html` file generated by javadoc used to contain an unsorted index. . Perhaps caused by packageFiles is a Map openjdk-7-jdk -> ./langtools.tar.bz2 -> src/share/classes/com/sun/tools/javadoc/JavadocTool.java . There was also a locale-specific wrapping issue, which has disappeared. This may be because enough things are using javahelper, which sets the locale. . Likely cause is jdk9_dev/langtools/src/jdk.javadoc/share/classes/com/sun/tools/javadoc/DocLocale.java +172 . Workaround is https://sources.debian.net/src/maven-debian-helper/latest/share/cdbs/1/class/maven.mk/?hl=136#L136 |
|
Packages in 'experimental' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |
|
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A # sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a P means a
pending bug while # indicates a
closed bug. In cases of several bugs, the symbol is repeated.