Skip to content

[MSHARED-271] Multiple reportSets don't work #37

@jira-importer

Description

@jira-importer

Max Schaefer opened MSHARED-271 and commented

Having several report sets only the last one is created.
Example: Create java doc report twice, with different parameters. First time with deprecated api list, second time without.
Expected behaviour: The two directories are created with the different javadocs.
However, currently onle one directory is created.

...
<reporting>
  <plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-javadoc-plugin</artifactId>
      <version>2.9</version>
      <reportSets>
        <reportSet>
          <id>without-deprecations</id>
          <configuration>
            <reportOutputDirectory>${project.reporting.outputDirectory}/myoutput</reportOutputDirectory>
            <destDir>myapidocs-without-deprecations</destDir>
            <nodeprecatedlist>true</nodeprecatedlist>
          </configuration>
          <reports>
            <report>javadoc</report>             
          </reports>
        </reportSet>
        <reportSet>
          <id>with-deprecations</id>
          <configuration>
            <reportOutputDirectory>${project.reporting.outputDirectory}/myoutput</reportOutputDirectory>
            <destDir>myapidocs-with-deprecations</destDir>
            <nodeprecatedlist>false</nodeprecatedlist>
          </configuration>
          <reports>
            <report>javadoc</report>             
          </reports>
        </reportSet>
      </reportSets>       
    </plugin>
  </plugins>
</reporting>

Affects: maven-reporting-exec-1.0.2

Attachments:

Issue Links:

  • MJAVADOC-335 In Maven 3 it is impossible to generate several JavaDoc reports at once
    ("is duplicated by")
  • SUREFIRE-905 Surefire report plugin only executed tests once. Junit Categorization is not possible
    ("is duplicated by")

5 votes, 4 watchers

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingpriority:criticalCrashes, loss of data, severe memory leak

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions