Adding more logs and try relative path 41/100841/1
authorChrisC <christophe.closset@intl.att.com>
Tue, 28 Jan 2020 08:26:47 +0000 (09:26 +0100)
committerChrisC <christophe.closset@intl.att.com>
Tue, 28 Jan 2020 08:28:30 +0000 (09:28 +0100)
Adding More logs to the scanner to understand why some sources are not taken into account + trying relative path for inclusion based on SonarCloud doc recommendation

Issue-ID: CLAMP-626
Signed-off-by: ChrisC <christophe.closset@intl.att.com>
Change-Id: Iccede3dc4c1e9a8f2c80ef3e763cbbcbdde489ab

pom.xml

diff --git a/pom.xml b/pom.xml
index c65216f..c66f2cf 100644 (file)
--- a/pom.xml
+++ b/pom.xml
@@ -93,8 +93,9 @@
                <!-- Enable language to disable javascript analysis -->
                <!-- <sonar.language>java</sonar.language> -->
                <!-- Parameters for Javascript coverage -->
+               <sonar.verbose>true</sonar.verbose>
                <sonar.sources>.</sonar.sources>
-               <sonar.inclusions>src/main/**,${project.build.directory}/${ui.react.src}/src/**</sonar.inclusions>
+               <sonar.inclusions>src/main/**,{ui.react.src}/src/**</sonar.inclusions>
                <sonar.exclusions>src/main/resources/**</sonar.exclusions>
                <sonar.scm.exclusions.disabled>true</sonar.scm.exclusions.disabled>
                <sonar.javascript.lcov.reportPaths>${project.build.directory}/${ui.react.src}/coverage/lcov.info</sonar.javascript.lcov.reportPaths>