Uploaded image for project: 'Maven Javadoc Plugin'
  1. Maven Javadoc Plugin
  2. MJAVADOC-437

javadoc:aggregate fails on initial build

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.10.3
    • Fix Version/s: 2.10.4
    • Component/s: None
    • Labels:
      None

      Description

      Scenario

      Take a SNAPSHOT version of a reactor project with at least two JAR modules.

      Assume that no artifacts of the given SNAPSHOT version have been built before (this is usually the case just after running release:perform).

      Actual Behaviour

      Now run mvn javadoc:aggregate. This build fails in the forked lifecycle. maven-javadoc-plugin unnecessarily tries to resolve the JAR artifacts of the current reactor (which are not avialable yet) and add them to the Javadoc classpath.

      Expected Behaviour

      Aggregated Javadoc should be generated without problems. It is sufficient to take the sources of the current reactor and only put external dependencies on the Javadoc classpath.

      This is a duplicate of an 8 year old bug MJAVADOC-116 with 51 votes which has been closed without being fixed.

      A patch for this problem was submitted in MJAVADOC-362, but does not seem to have received attention by committers. (I admit the problem description is not very clear.)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                michael-o Michael Osipov
                Reporter:
                hwellmann Harald Wellmann
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: