CODEWITHSUNDEEP
javamavenbuildpom.xml
chao
chao

Reputation: 2024

Global changes to maven surefire plugin in .m2/settings.xml

I would like to change the default setting for maven-surefire-plugin, and instead of using <reportFormat>brief</reportFormat>, I would like to use <reportFormat>plain</reportFormat>.

Usually, I would achieve this by modifying an individual pom for a project, such as:

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-surefire-plugin</artifactId>
    <configuration>
        <redirectTestOutputToFile>true</redirectTestOutputToFile>
        <reportFormat>plain</reportFormat>
    </configuration>
</plugin>

However, is it possible to somehow modify ~/.m2/settings.xml file and set <reportFormat>plain</reportFormat> as a default behaviour for all maven projects I want to compile. I do an analysis of many maven projects, so I would prefer to change the behaviour on global level rather than modifying pom files for each individual project.

Upvotes: 1

Views: 461

Answers (1)

davidxxx
davidxxx

Reputation: 131456

The settings.xml configuration file doesn't go down at this level of detail. The plugin configuration can be specified only in the pom.xml
The best way to check it is studying the settings.xml schema :

https://maven.apache.org/xsd/settings-1.0.0.xsd

You could see that the single elements referencing the "plugin" word have no relation with the plugin configuration in the build.

For your requirement, the single solution that has also its drawbacks if bad used is using a parent pom that defines the plugin configuration and that all Maven modules should have as parent to inherit from the plugin configuration and potentially from other things.

If your applicative projets use a multi module/parent pom structure, I think that a nicer solution would be to declare this configuration in the parent pom of each multi module/parent pom.
In this way you declare it multiple times but a single time by set of related projects.

Upvotes: 1

Related Questions