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

aggregate-jar does nothing if called as part of a reactor build

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Cannot Reproduce
    • 2.9.1
    • None
    • None
    • None
    • Reproduced with Oracle Java 1.7.0_45, Maven 3.0.5. Also reproduced with Maven 3.2.2.

    Description

      The attached reproduction.tgz contains a multi-module project com.repo:parent, and two child modules, com.repo:module_a and com.repo:module_b. com.repo:module-a is a jar module that contains a Java class. com.repo:module-b depends on com.repo:module-a and has uses javadoc:aggregate-jar to create a javadoc attachment.

      If I change into the module_b directory and run mvn clean install, a com.repo:module-b:javadoc attachment is not created.

      However, if I run mvn clean install from the top level, a com.repo:module-b:javadoc attachment is not created. I believe this to be a bug.

      Running with -X shows that the aggregate-jar mojo is configured, but never executed.

      If I change to module-b and run with -X, I see an MultipleArtifactsNotFoundException, but it otherwise behaves as I would expect. This looks similar to the symptoms of MVN-4618.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            rfscholte Robert Scholte
            philipa Philip Aston
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment