You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by gg...@apache.org on 2025/02/27 16:14:26 UTC

(commons-build-plugin) branch master updated: Bullet proof the test coverage instructions

This is an automated email from the ASF dual-hosted git repository.

ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-build-plugin.git


The following commit(s) were added to refs/heads/master by this push:
     new b45deaa  Bullet proof the test coverage instructions
b45deaa is described below

commit b45deaad7538e07edee728c4681c8d8d88464196
Author: Gary Gregory <ga...@gmail.com>
AuthorDate: Thu Feb 27 11:14:21 2025 -0500

    Bullet proof the test coverage instructions
---
 src/main/resources/commons-xdoc-templates/readme-md-template.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/main/resources/commons-xdoc-templates/readme-md-template.md b/src/main/resources/commons-xdoc-templates/readme-md-template.md
index 94e2158..7caaf8e 100644
--- a/src/main/resources/commons-xdoc-templates/readme-md-template.md
+++ b/src/main/resources/commons-xdoc-templates/readme-md-template.md
@@ -90,7 +90,7 @@ There are some guidelines which will make applying PRs easier for us:
 + Create minimal diffs - disable on save actions like reformat source code or organize imports. If you feel the source code should be reformatted create a separate PR for this change.
 + Provide JUnit tests for your changes and make sure your changes don't break any existing tests by running `mvn`.
 + Before you pushing a PR, run `mvn` (by itself), this runs the default goal, which contains all build checks.
-+ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false`
++ To see the code coverage report, regardless of coverage failures, run `mvn clean site -Dcommons.jacoco.haltOnFailure=false -Pjacoco`
 
 If you plan to contribute on a regular basis, please consider filing a [contributor license agreement](https://www.apache.org/licenses/#clas).
 You can learn more about contributing via GitHub in our [contribution guidelines](CONTRIBUTING.md).