Fail the build when naming conventions violated (#3974)

* Failing build if unit test name does not follow one of the following conventions : ..IntegrationTest, ..LongRunningUnitTest, ..ManualTest, ..JdbcTest, ..LiveTest

* Custom PMD Rules project

* Fixed this issue when unit test classes were not being scanned by custom PMD rule (This happened after I pulled code from upstream project)

* Don't fail the build if PMD custom rule fails

* Reconfigure PMD

* Reformat POM

* Adjust PMD rules

* Rename test

custom-pmd/pom.xml

@@ -0,0 +1,43 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+	xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+	<modelVersion>4.0.0</modelVersion>
+	<groupId>org.baeldung.pmd</groupId>
+	<artifactId>custom-pmd</artifactId>
+	<version>0.0.1-SNAPSHOT</version>
+	<packaging>jar</packaging>
+	<name>custom-pmd</name>
+	<url>http://maven.apache.org</url>
+
+	<properties>
+		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
+		<maven-compiler-plugin.version>3.7.0</maven-compiler-plugin.version>
+		<pmdVersion>6.0.1</pmdVersion>
+	</properties>
+
+	<dependencies>
+	    <dependency> 
+           <groupId>net.sourceforge.pmd</groupId> 
+           <artifactId>pmd-core</artifactId> 
+           <version>${pmdVersion}</version> 
+        </dependency>
+	    <dependency>
+	      <groupId>net.sourceforge.pmd</groupId>
+	      <artifactId>pmd-java</artifactId>
+	      <version>${pmdVersion}</version>
+	    </dependency>
+	</dependencies>
+	
+	<build>
+		<plugins>
+			<plugin>
+		         <groupId>org.apache.maven.plugins</groupId>
+		         <artifactId>maven-compiler-plugin</artifactId>
+		         <version>${maven-compiler-plugin.version}</version>
+		         <configuration>
+		             <source>1.8</source>
+		             <target>1.8</target>
+		         </configuration>
+		    </plugin>
+	    </plugins>
+    </build>
+</project>