Uploaded image for project: 'Maven Site Plugin'
  1. Maven Site Plugin
  2. MSITE-454

Don't use aggregator mojos for default report set

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 3.4
    • None
    • None

    Description

      For a POM snippet

      <reporting>
  <plugins>
    <plugin>
      <artifactId>maven-javadoc-plugin</artifactId>
    </plugin>
  </plugins>
</reporting>

      all available mojos of the plugin will be used as reports. This includes mojos marked with @aggregator although binding aggregators into the lifecycle can be troublesome, especially if they additionally fork the lifecycle.

      Hence I suggest we exclude aggregators from report sets unless explicitly configured by the user.

      Attachments

        Issue Links

          depends upon

          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
          is related to

          Bug - A problem which impairs or prevents the functions of the product. MJAVADOC-171 Modules in multi-module projects are "built" too often

          • 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

          Activity

            People

              hboutemy Herve Boutemy
              bentmann Benjamin Bentmann
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: