adding victi.ms and direct-dependency enforcer rules

Author: jdcasey

pom.xml

@@ -173,6 +173,16 @@
               <artifactId>enforce-managed-deps-rule</artifactId>
               <version>1.0</version>
             </dependency>
+            <dependency>
+              <groupId>de.is24.maven.enforcer.rules</groupId>
+              <artifactId>illegal-transitive-dependency-check</artifactId>
+              <version>1.7.4</version>
+            </dependency>
+            <dependency>
+              <groupId>com.redhat.victims</groupId>
+              <artifactId>enforce-victims-rule</artifactId>
+              <version>1.3.4</version>
+            </dependency>
           </dependencies>
           <executions>
             <execution>
@@ -198,6 +208,52 @@
                     <banSnapshots />
                     <unCheckedPluginList>org.eclipse.m2e:lifecycle-mapping</unCheckedPluginList>
                   </requirePluginVersions>
+                  <illegalTransitiveDependencyCheck implementation="de.is24.maven.enforcer.rules.IllegalTransitiveDependencyCheck">
+                    <reportOnly>false</reportOnly>
+                    <regexIgnoredClasses>
+                        <regexIgnoredClass>com\.sun\.net\.httpserver\..+</regexIgnoredClass>
+                        <regexIgnoredClass>javax\..+</regexIgnoredClass>
+                        <regexIgnoredClass>org\.w3c\.dom\..+</regexIgnoredClass>
+                        <regexIgnoredClass>org\.xml\.sax\..+</regexIgnoredClass>
+                    </regexIgnoredClasses>
+                    <useClassesFromLastBuild>true</useClassesFromLastBuild>
+                  </illegalTransitiveDependencyCheck>
+                  <victimsCheck implementation="com.redhat.victims.VictimsRule">     
+                    <!-- 
+                      Check the project's dependencies against the database using 
+                      name and version. The default mode for this is 'warning'.
+
+                      Valid options are: 
+
+                      disabled: Rule is still run but only INFO level messages aand no errors.
+                      warning : Rule will spit out a warning message but doesn't result in a failure. 
+                      fatal   : Rule will spit out an error message and fail the build. 
+                    -->
+                    <metadata>warning</metadata>
+                    <!--
+                      Check the project's dependencies against the database using 
+                      the SHA-512 checksum of the artifact. The default is fatal. 
+
+                      Valid options are: 
+
+                      disabled: Rule is still run but only INFO level messages aand no errors.
+                      warning : Rule will spit out a warning message but doesn't result in a failure. 
+                      fatal   : Rule will spit out an error message and fail the build. 
+                    -->
+                    <fingerprint>fatal</fingerprint>
+                    <!-- 
+                      Disables the synchronization mechansim. By default the rule will 
+                      attempt to update the database for each build. 
+
+                      Valid options are: 
+
+                      auto  : Automatically update the database entries on each build.
+                      daily : Update the database entries once per day.
+                      weekly: Update the database entries once per week.
+                      offline   : Disable the synchronization mechanism.
+                    -->  
+                    <updates>auto</updates>
+                  </victimsCheck>
                 </rules>
               </configuration>
             </execution>