From 09d4f069e48a0b4ab7359bbcc3b299d222721230 Mon Sep 17 00:00:00 2001 From: vempo Date: Tue, 29 Aug 2017 18:15:04 +0300 Subject: Set up static analysis for on-boarding Configured PMD Maven plugin in the onboarding pom.xml, with a custom ruleset. Currently disabled by default, can be ran on demand. Change-Id: I0e7ba1aeb1aefcea86fc2534ebc62343057f7c34 Issue-ID: SDC-246 Signed-off-by: vempo --- .../src/main/resources/build-pmd-ruleset.xml | 42 ++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 build-tools/src/main/resources/build-pmd-ruleset.xml (limited to 'build-tools/src/main/resources') diff --git a/build-tools/src/main/resources/build-pmd-ruleset.xml b/build-tools/src/main/resources/build-pmd-ruleset.xml new file mode 100644 index 0000000000..dd8984a970 --- /dev/null +++ b/build-tools/src/main/resources/build-pmd-ruleset.xml @@ -0,0 +1,42 @@ + + + + + Essential rules according to SonarQube. Note that it is impossible to make PMD rules exactly match the + SonarQube ones, but they will probably catch about 90% of violations before they get into the source control. + The advantage is that PMD can be ran locally on any development setup and does not require a license. + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file -- cgit 1.2.3-korg