Maven Report Configuration vs Build Configuration

Vitaly

It is interesting what is the differences between

report->configuration element and build->configuration element in POM.

It is written in POM references:

Subtle difference is that a plugin configuration under the reporting element works as build plugin configuration, although the opposite is not true (a build plugin configuration does not affect a reporting plugin).

See http://maven.apache.org/pom.html#Reporting

Could you give particular example of the differences in behaviour?

Vitaly

This statement means the following:

If we have report generation plugin configuration like

  <build>
      <plugins>
          <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-project-info-reports-plugin</artifactId>
              <version>2.8</version>

              <configuration>
                  <linkOnly>true</linkOnly>
              </configuration>
          </plugin>
      </plugins>
  </build>

then linkOnly configuration property won't be used when invoking site generation command

mvn site

Instead, we should use the same configuration under reporting element:

  <reporting>
      <plugins>
          <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-project-info-reports-plugin</artifactId>
              <version>2.8</version>

              <configuration>
                  <linkOnly>true</linkOnly>
              </configuration>

              <reportSets>
                  <reportSet>
                      <reports>
                          <report>license</report>
                      </reports>
                  </reportSet>
              </reportSets>
          </plugin>
      </plugins>
  </reporting>

Here we generate only license report with configuration parameter linkOnly=true.

I.e. build configuration is not used.

Note: If we explicitly invoke report generation goal "license"

mvn project-info-report:license

then it will use configuration under build element. I.e. we have opposite behaviour here.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

From Dev

Execution VS Configuration in Maven

From Dev

A maven build configuration with this name already exists

From Dev

A maven build configuration with this name already exists

From Dev

Maven Configuration

From Java

Maven Jacoco Configuration - Exclude classes/packages from report not working

From Dev

Share maven plugin configuration between build and reporting sections

From Dev

Maven build process ERROR involve with Anypoint Studio configuration (ArrayIndexOutOfBoundsException: 15469)

From Dev

sbt Configuration vs Ivy configuration

From Dev

Intellij Run Configuration Spring Boot vs Maven Issues

From Dev

Maven Java EE Configuration

From Dev

Jersey Maven configuration

From Dev

maven bundle plugin configuration

From Dev

Jersey Maven configuration

From Dev

Maven version control configuration

From Dev

Html report configuration for Jmeter Test

From Dev

Adding a build configuration in Xcode

From Dev

Programmatically check the build configuration

From Dev

Build configuration history in teamcity

From Dev

TeamCity Build Chain configuration

From Dev

Oasis build configuration with subdirectories

From Dev

Programmatically check the build configuration

From Dev

Configuration of plugin build for Jenkins

From Dev

Adding a scheduled build to the build configuration

From Dev

auto-generated sources and cmake configuration: developer build vs user build

From Dev

Spring @Component vs @Configuration for basic configuration class

From Dev

How to build a VS2015 solution that has a VS2010 configuration using MSBuild?

From Dev

Eclipse android Maven : Plugin execution not covered by lifecycle configuration (execution: ndk- build, phase: compile)

From Dev

Why can't Maven build resolve Spring @Bean @Configuration etc annotations?

From Dev

Spring-boot with maven configuration

Related Related

  1. 1

    Execution VS Configuration in Maven

  2. 2

    A maven build configuration with this name already exists

  3. 3

    A maven build configuration with this name already exists

  4. 4

    Maven Configuration

  5. 5

    Maven Jacoco Configuration - Exclude classes/packages from report not working

  6. 6

    Share maven plugin configuration between build and reporting sections

  7. 7

    Maven build process ERROR involve with Anypoint Studio configuration (ArrayIndexOutOfBoundsException: 15469)

  8. 8

    sbt Configuration vs Ivy configuration

  9. 9

    Intellij Run Configuration Spring Boot vs Maven Issues

  10. 10

    Maven Java EE Configuration

  11. 11

    Jersey Maven configuration

  12. 12

    maven bundle plugin configuration

  13. 13

    Jersey Maven configuration

  14. 14

    Maven version control configuration

  15. 15

    Html report configuration for Jmeter Test

  16. 16

    Adding a build configuration in Xcode

  17. 17

    Programmatically check the build configuration

  18. 18

    Build configuration history in teamcity

  19. 19

    TeamCity Build Chain configuration

  20. 20

    Oasis build configuration with subdirectories

  21. 21

    Programmatically check the build configuration

  22. 22

    Configuration of plugin build for Jenkins

  23. 23

    Adding a scheduled build to the build configuration

  24. 24

    auto-generated sources and cmake configuration: developer build vs user build

  25. 25

    Spring @Component vs @Configuration for basic configuration class

  26. 26

    How to build a VS2015 solution that has a VS2010 configuration using MSBuild?

  27. 27

    Eclipse android Maven : Plugin execution not covered by lifecycle configuration (execution: ndk- build, phase: compile)

  28. 28

    Why can't Maven build resolve Spring @Bean @Configuration etc annotations?

  29. 29

    Spring-boot with maven configuration

HotTag

Archive