Maven profiles allow customizing a build for different environments by setting or overriding default configuration values. Profiles are defined in the pom.xml and can be activated via command line flags. This document discusses using Maven profiles to generate both Allure and JaCoCo reports from the same project, with one profile for Allure and another solely to produce the JaCoCo report required by SonarQube for code coverage analysis. Examples and references are provided.

1. # 1 9 - M AV E N P R O F I L E
allure sonarqube

2. W H AT I S ?
• A profile in Maven is an alternative set of configuration values which set or
override default values. Using a profile, you can customize a build for
different environments. Profiles are configured in the pom.xml and are
given an identifier.
• Then you can run Maven with a command-line flag that tells Maven to
execute goals in a specific profile.

3. W H Y ?
• Using Allure for report on the project bcn-jug-allure-junit5 I was able to
provide to SonarQube the JaCoCo report and then the SonarQube cannot
provide the code coverage.
• One option is use profile and use one profile as default for Allure and
another only to generate the JaCoCo report, since is required by
SonarQube

4. E XA M P L E - P O M . X M L

5. E XA M P L E - AC T I O N .Y M L

6. R E S U LT - R E P O R T + C OV E R AG E

7. R E F E R E N C E S
• [1] -https://maven.apache.org/guides/introduction/introduction-to-
profiles.html
• [2] - https://github.com/luizgustavocosta/bcn-jug-allure-junit5