TEMP: add mock-violations file to validate annotations (REVERT BEFORE MERGE)

Author: joaodinissf

com.avaloq.tools.ddk/src/com/avaloq/tools/ddk/MockViolations.java

@@ -0,0 +1,36 @@
+/*******************************************************************************
+ * Copyright (c) 2026 Avaloq Group AG
+ *
+ * MOCK FILE — DO NOT MERGE.
+ * Introduces 1 PMD + 1 Checkstyle + 1 SpotBugs violation each to validate that the
+ * static-analysis job's Python annotation step renders inline PR annotations.
+ * This file MUST be reverted before this PR is marked ready for review.
+ *******************************************************************************/
+package com.avaloq.tools.ddk;
+
+@SuppressWarnings("PMD.SystemPrintln")
+public class MockViolations {
+
+  // PMD: EmptyCatchBlock — empty catch block (errorprone.xml category, in the project ruleset)
+  public void pmdViolation() {
+    try {
+      Class.forName("Foo");
+    } catch (Exception e) {
+    }
+  }
+
+  // Checkstyle: EmptyCatchBlock — same body as above; both PMD and Checkstyle should fire on the
+  // empty catch block. Using a distinct method so the two annotations land on different lines.
+  public void checkstyleViolation() {
+    try {
+      Class.forName("Bar");
+    } catch (Exception e) {
+    }
+  }
+
+  // SpotBugs: DM_DEFAULT_ENCODING — String#getBytes() without an explicit charset.
+  public byte[] spotbugsViolation(final String s) {
+    return s.getBytes();
+  }
+
+}