You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@phoenix.apache.org by ch...@apache.org on 2020/05/14 07:08:51 UTC
[phoenix] branch master updated: PHOENIX-5892 Add code coverage
steps in build documentation
This is an automated email from the ASF dual-hosted git repository.
chinmayskulkarni pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/phoenix.git
The following commit(s) were added to refs/heads/master by this push:
new 49599fd PHOENIX-5892 Add code coverage steps in build documentation
49599fd is described below
commit 49599fd89b6cfa9cab9d7d3f6dcf4bdc5428915a
Author: Sandeep Guggilam <sg...@sandeepg-ltm.internal.salesforce.com>
AuthorDate: Wed May 13 09:39:15 2020 -0700
PHOENIX-5892 Add code coverage steps in build documentation
Signed-off-by: Chinmay Kulkarni <ch...@apache.org>
---
BUILDING.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/BUILDING.md b/BUILDING.md
index 08f67af..dc75d21 100644
--- a/BUILDING.md
+++ b/BUILDING.md
@@ -83,7 +83,11 @@ All Unit Tests and Integration tests
`$ mvn clean verify`
The verify maven target will also run dependency:analyze-only, which checks if the dependencies
- used in the code and declared in the maven projects match.
+ used in the code and declared in the maven projects match. The code coverage report would be
+generated at /target/site/jacoco/index.html
+
+To skip code coverage analysis
+`$ mvn verify -Dskip.code-coverage`
Findbugs
--------