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

Modules in multi-module projects are "built" too often

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.3
    • None
    • None
    • None
    • Maven 2.0.8, Linux

    Description

      In a multi-module project, all modules are "built" twice for each module. This leads to huge performance problems when many modules are in a project. In the attached sample project, the xmlbeans plugin is executed 27 times for a project with one parent module and two submodules. 18 of these executions can be attributed to the javadoc plugin. With version 2.2, only 3 invocations (once for each project) are caused by the javadoc plugin.

      Attachments

        1. 2.2.log
          7 kB
        2. 2.3.log
          15 kB
        3. mjavadoc171.patch
          0.5 kB
          Daniel Fabulich
        4. mjavadoc-171.zip
          2 kB
        5. mjavadoc-171-b.zip
          14 kB
          Herve Boutemy
        6. mjavadoc-171-fixed-M3.zip
          27 kB
          Herve Boutemy
        7. mvnexec.zip
          3 kB

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SUREFIRE-449 In multi-module projects, all tests are run for each module in the module tree

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MSHARED-266 run aggregator reports only when current projet is pom packaging and has modules

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MSHARED-333 display what phase or goal is forked by a report

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MNG-2184 Possible problem with @aggregator and forked lifecycles

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MJAVADOC-137 javadoc:javadoc always runs as "aggregator"

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MSITE-454 Don't use aggregator mojos for default report set

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. MNG-5170 prevent mojo to fork lifecycle when same lifecycle is already executed

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              hboutemy Herve Boutemy
              seidler Stefan Seidel
              Votes:
              16 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: