Skip irrelevant modules when using Sonarqube 5.x
authorMarc-Andre Laperle <marc-andre.laperle@ericsson.com>
Fri, 22 Apr 2016 21:33:09 +0000 (17:33 -0400)
committerMarc-Andre Laperle <marc-andre.laperle@ericsson.com>
Sat, 30 Apr 2016 23:21:55 +0000 (19:21 -0400)
commitdf0d516959d4c77c1695d0d43b7f1b52cd212e83
tree71aea90187a25e3a9bf07f75fa144e88fa5b1cfa
parentd12b792bc4422fe65522cf1420a94f1df041f90f
Skip irrelevant modules when using Sonarqube 5.x

sonar.skippedModules is depracated and will not work in more recent
versions of Sonarqube. We can define sonar.skip in respective modules
instead. Both properties can be defined without problem. To preserve
the pom-less build, a new profile is activated in the presence of the
sonar.skip.properties file. So each module we do not want to analyse
with maven have to contain this file.

Change-Id: I6bf8115540744e48a9431f63ba96c504917f35e3
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/71270
Reviewed-by: Hudson CI
Reviewed-by: Matthew Khouzam <matthew.khouzam@ericsson.com>
ctf/org.eclipse.tracecompass.ctf.parser/sonar.skip.properties [new file with mode: 0644]
doc/org.eclipse.tracecompass.examples/sonar.skip.properties [new file with mode: 0644]
pom.xml
This page took 0.024494 seconds and 5 git commands to generate.