-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b171
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8181350 | 10 | Magnus Ihse Bursie | P3 | Resolved | Fixed | b10 |
JDK-8181233 | 9.0.4 | Magnus Ihse Bursie | P3 | Resolved | Fixed | b01 |
When the build system tries to figure out which modules that should be included by the javadoc build, it locates the set of modules "required" by already included modules, starting from an initial set and repeating recursively (a method which we unfortunately called "transitive").
However, for javadoc, we should only look at those re-exported modules that are classified by a "requires transitive" relationship (which I therefore have called "re-exported" to not clash with the established term "transitive").
The effect of getting this wrong is e.g. that we copy module graph png files that we should not, and that we look at too broad a set of files for looking at changes that should trigger a re-build of the javadoc.
However, for javadoc, we should only look at those re-exported modules that are classified by a "requires transitive" relationship (which I therefore have called "re-exported" to not clash with the established term "transitive").
The effect of getting this wrong is e.g. that we copy module graph png files that we should not, and that we look at too broad a set of files for looking at changes that should trigger a re-build of the javadoc.
- backported by
-
JDK-8181233 Use "requires transitive" relationship when determining modules for javadoc
-
- Resolved
-
-
JDK-8181350 Use "requires transitive" relationship when determining modules for javadoc
-
- Resolved
-