From 1929d75c6856e212979c3a9c7950dfd717d3bb98 Mon Sep 17 00:00:00 2001 From: vempo Date: Sun, 12 Aug 2018 14:17:59 +0300 Subject: Removed execution of PMD from build Change-Id: I52d55e2585c56118c685745c00e52c2838b76d04 Issue-ID: SDC-1065 Signed-off-by: vempo --- .../src/main/resources/build-pmd-ruleset.xml | 42 ---------------------- 1 file changed, 42 deletions(-) delete mode 100644 build-tools/src/main/resources/build-pmd-ruleset.xml (limited to 'build-tools/src/main/resources/build-pmd-ruleset.xml') diff --git a/build-tools/src/main/resources/build-pmd-ruleset.xml b/build-tools/src/main/resources/build-pmd-ruleset.xml deleted file mode 100644 index dd8984a970..0000000000 --- a/build-tools/src/main/resources/build-pmd-ruleset.xml +++ /dev/null @@ -1,42 +0,0 @@ - - - - - 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