Create rule S8314: Static imports should appear before regular imports

rules/S8314/groovy/metadata.json

@@ -0,0 +1,24 @@
+{
+  "title": "Static imports should appear before regular imports",
+  "type": "CODE_SMELL",
+  "status": "ready",
+  "remediation": {
+    "func": "Constant/Issue",
+    "constantCost": "5 min"
+  },
+  "tags": [],
+  "defaultSeverity": "Critical",
+  "ruleSpecification": "RSPEC-8314",
+  "sqKey": "S8314",
+  "scope": "Main",
+  "defaultQualityProfiles": [
+    "Sonar way"
+  ],
+  "quickfix": "unknown",
+  "code": {
+    "impacts": {
+      "MAINTAINABILITY": "HIGH"
+    },
+    "attribute": "CONVENTIONAL"
+  }
+}

rules/S8314/groovy/rule.adoc

@@ -0,0 +1,29 @@
+This rule raises an issue when static imports are declared after regular (non-static) imports in a source file.
+
+== Why is this an issue?
+
+Import statements should follow a consistent order to keep code readable and easy to scan. In Java and Groovy, the usual convention is to place all static imports before regular imports.
+
+== How to fix it
+
+Place all static imports together before regular imports in the import section.
+
+=== Code examples
+
+==== Noncompliant code example
+
+[source,groovy,diff-id=1,diff-type=noncompliant]
+----
+import java.util.ArrayList
+import static java.lang.Math.PI // Noncompliant
+----
+
+==== Compliant solution
+
+[source,groovy,diff-id=1,diff-type=compliant]
+----
+import static java.lang.Math.PI
+import java.util.ArrayList
+----
+
+

rules/S8314/metadata.json

@@ -0,0 +1,2 @@
+{
+}