Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8189056

javadoc target for stable specdiff comparisons

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 10
    • Fix Version/s: 10
    • Component/s: infrastructure
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b29

      Description

      For JSR 383 (Java SE 18.3), we need weekly diffs of the Java SE 18.3 API specification. The current "doc-javase" makefile target always uses the most recent version of the javadoc tool (i.e. the tool that was just built). Unfortunately, this introduces unwanted diffs that are due to changes in the javadoc tool's formatting of the specification. A means to use a fixed version of the javadoc tool so that the only detected changes are those to the specification itself is needed.

      Erik provides the following thoughts:

      For creating comparisons of 18.3 every week, I think we need to introduce another javadoc target for this specific purpose, where we can lock down the parameters to be exactly what was used for 9+181. This also relies on us changing boot jdk for 18.3 to 9+181 (which we should do now anyway) and having this new javadoc target use the javadoc of the bootjdk. That way we have control of the output so you should be able to do meaningful clean comparisons.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ihse Magnus Ihse Bursie
                Reporter:
                iris Iris Clark
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: