Uploaded image for project: 'Java Parent Project'
  1. Java Parent Project
  2. JPAR-104 Support Java 11
  3. JPAR-129

Javadoc built with Java 11 does not include platform APIs



    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 7.11.0
    • Fix Version/s: 11.0.0
    • Labels:


      There are a significant number of bugs in the maven-javadoc-plugin and in the JDK's javadoc tool. The lists of bugs evolve between versions and interact with each other in unpleasant ways.

      As things stand today, although per JPAR-122 it is possible with maven-javadoc-plugin 3.0.1 to avoid NPEs while building with Java 11 (as we'll need to do for the V11 product platform), it does not appear to be possible to fully populate links to either the Java EE API or to the platform API. The most common excursion from correct behaviour is a message to the effect that the referenced API has packages in the unnamed module (which is true for Java EE 5 and Java 8) and that this is not compatible with a modular build (which we're not doing). 

      The relevant bugs seem to be MJAVADOC-555 and JDK-8212233, but there may be others. It is possible that maven-javadoc-plugin 3.1.0 will resolve this. When it comes out, at least, we should look at this again and see if we can thread our way between Scylla and Charybdis once more.


          Issue Links



              • Assignee:
                ian@iay.org.uk Ian Young
                ian@iay.org.uk Ian Young
              • Watchers:
                2 Start watching this issue


                • Created:

                  Time Tracking

                  Original Estimate - Not Specified
                  Not Specified
                  Remaining Estimate - Not Specified
                  Not Specified
                  Time Spent - 1 day, 30 minutes
                  1d 30m