Initial works to add spotless (#64)

* Initial works to add spotless
* New upgrade
* Tested spotless

Author: jabrena

.cursor/rules/111-java-maven-deps-and-plugins.mdc

@@ -7,6 +7,11 @@ alwaysApply: false
 
 This rule provides a comprehensive, conversational approach to updating Maven pom.xml files with properties, dependencies, plugins, and profiles. It MUST ask questions first to understand the project needs and then conditionally add only relevant components.
 
+**⚠️ CRITICAL: NO CACHING OF QUESTIONS ⚠️**
+- NEVER use cached or remembered questions from previous interactions
+- ALWAYS read the template file fresh using file_search and read_file tools
+- Verify all questions and options match the current template content exactly
+
 ## Pre-requisites Check
 
 **CRITICAL**: This step MUST be completed before proceeding to any subsequent steps. Do NOT continue with Step 1 (Project Assessment Questions) until the Maven Wrapper question is fully resolved.
@@ -61,9 +66,11 @@ This rule provides a comprehensive, conversational approach to updating Maven po
 
 **MANDATORY PROCESS:**
 
-1. **Reference the Template**: Use the questions from [java-maven-questions-template.md](mdc:.cursor/rules/templates/java-maven-questions-template.md)
+1. **ALWAYS READ THE TEMPLATE FRESH**: Before asking any questions, you MUST use the `file_search` and `read_file` tools to locate and read the complete content of `java-maven-questions-template.md`. DO NOT use cached or remembered questions from previous interactions.
+
+2. **Reference the Template**: Use the questions from [java-maven-questions-template.md](mdc:.cursor/rules/templates/java-maven-questions-template.md)
 
-2. **STRICT ENFORCEMENT RULES:**
+3. **STRICT ENFORCEMENT RULES:**
    - ✅ Ask questions **ONE BY ONE** in the exact order specified in the template
    - ✅ **WAIT** for user response to each question before proceeding to the next
    - ✅ Use the **EXACT wording** from the template questions
@@ -73,15 +80,20 @@ This rule provides a comprehensive, conversational approach to updating Maven po
    - ✅ **Do NOT** assume answers or provide defaults
    - ✅ **Do NOT** skip questions or change their order
 
-3. **QUESTION SEQUENCE** (from template):
+4. **QUESTION SEQUENCE** (from template - MUST BE READ FRESH EACH TIME):
    - **Question 1**: [Project Nature](mdc:.cursor/rules/templates/java-maven-questions-template.md#1-project-nature) (single selection from the template)
    - **Question 2**: [Java Version](mdc:.cursor/rules/templates/java-maven-questions-template.md#2-java-version) (single selection from the template)
    - **Question 3**: [Build and Quality Aspects](mdc:.cursor/rules/templates/java-maven-questions-template.md#3-build-and-quality-aspects) (multiple selection allowed from the template)
    - **Question 4**: [Coverage Threshold](mdc:.cursor/rules/templates/java-maven-questions-template.md#4-coverage-threshold) (conditional - only if coverage selected)
    - **Question 5**: [Sonar Configuration](mdc:.cursor/rules/templates/java-maven-questions-template.md#5-sonar-configuration-conditional) (conditional - only if static analysis with Sonar selected)
    - **Question 6**: [Sonar Host Configuration](mdc:.cursor/rules/templates/java-maven-questions-template.md#6-sonar-host-configuration-conditional) (conditional - only if Sonar configuration enabled)
 
-4. **VALIDATION CHECKPOINT:**
+5. **TEMPLATE VERIFICATION STEP:**
+   - Before asking questions, verify that ALL options from the template are included
+   - Cross-check your question content against the freshly read template file
+   - If there are discrepancies, re-read the template and correct your questions
+
+6. **VALIDATION CHECKPOINT:**
    - **STOP** and verify all applicable questions have been answered
    - **Do NOT proceed** to Step 2 until complete responses received
    - **Confirm** understanding of user selections before implementation

.cursor/rules/templates/java-maven-plugins-template.md

@@ -6,43 +6,7 @@ This template provides Maven plugin configurations that should be added conditio
 
 ## Core Plugins
 
-### Add maven-plugin-enforcer (Enhanced)
-
-**When to use**: Always recommended for build consistency and dependency management.
-**User question**: "Do you want enhanced dependency validation and build enforcement? (y/n)"
-
-Nature: General
-Category: Build
-
-Update the pom.xml with this enhanced enforcer plugin:
-
-```xml
-<plugin>
-    <groupId>org.codehaus.mojo</groupId>
-    <artifactId>flatten-maven-plugin</artifactId>
-    <version>${maven-plugin-flatten.version}</version>
-    <configuration>
-    </configuration>
-    <executions>
-        <execution>
-            <id>flatten</id>
-            <phase>process-resources</phase>
-            <goals>
-                <goal>flatten</goal>
-            </goals>
-        </execution>
-        <execution>
-            <id>flatten.clean</id>
-            <phase>clean</phase>
-            <goals>
-                <goal>clean</goal>
-            </goals>
-        </execution>
-    </executions>
-</plugin>
-```
-
-## Add maven-plugin-enforcer
+### Add maven-plugin-enforcer
 
 Nature: General
 Category: Build
@@ -157,6 +121,44 @@ Update the pom.xml with this new plugin:
 
 ## Optional Build Enhancement Plugins
 
+### Add spotless-maven-plugin
+
+Nature: General
+Category: Build
+
+Update the pom.xml with this plugin:
+
+```xml
+<plugin>
+    <groupId>com.diffplug.spotless</groupId>
+    <artifactId>spotless-maven-plugin</artifactId>
+    <version>${maven-plugin-spotless.version}</version>
+    <configuration>
+        <encoding>UTF-8</encoding>
+        <java>
+            <removeUnusedImports />
+            <importOrder>
+                <order>,\#</order>
+            </importOrder>
+            <endWithNewline />
+            <trimTrailingWhitespace />
+            <indent>
+                <spaces>true</spaces>
+                <spacesPerTab>4</spacesPerTab>
+            </indent>
+        </java>
+    </configuration>
+    <executions>
+        <execution>
+            <goals>
+                <goal>check</goal>
+            </goals>
+            <phase>process-sources</phase>
+        </execution>
+    </executions>
+</plugin>
+```
+
 ### Add flatten-maven-plugin
 
 **When to use**: For library projects that will be published to Maven repositories.

.cursor/rules/templates/java-maven-properties-template.md

@@ -57,6 +57,12 @@ Start with essential build properties that every project needs (use the Java ver
 
 **Only add plugin version properties for selected features**:
 
+### Static Analysis
+**If Format source code selected**:
+```xml
+<maven-plugin-spotless.version>2.44.5</maven-plugin-spotless.version>
+```
+
 ### Integration Testing
 **If Integration Testing selected**:
 ```xml

.cursor/rules/templates/java-maven-questions-template.md

@@ -28,6 +28,7 @@ Options:
 **What build and quality aspects are important for your project?** (Select all that apply)
 
 Options:
+- Format source code (Spotless)
 - Compiler behaviour improvements with ErrorProne + NullAway (Ask for JSpecify)
 - Integration testing (Failsafe)
 - Code coverage reporting (JaCoCo)

examples/maven-demo/README-DEV.md

@@ -16,6 +16,9 @@
 # Clean and package in one command
 ./mvnw clean package
 
+#Format source code
+./mvnw spotless:apply
+
 # Run integration tests
 ./mvnw verify
 

examples/maven-demo/pom.xml

@@ -9,10 +9,18 @@
   <version>1.0-SNAPSHOT</version>
 
   <properties>
+    <java.version>21</java.version>
+    <maven.version>3.9.10</maven.version>
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
-    <maven.compiler.release>17</maven.compiler.release>
+    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
+    <maven.compiler.release>${java.version}</maven.compiler.release>
 
+    <!-- Dependency versions -->
     <assertj.version>3.27.3</assertj.version>
+
+    <!-- Plugin versions -->
+    <maven-plugin-spotless.version>2.44.5</maven-plugin-spotless.version>
+
   </properties>
 
   <dependencyManagement>
@@ -49,5 +57,35 @@
   </dependencies>
 
   <build>
+    <plugins>
+      <plugin>
+        <groupId>com.diffplug.spotless</groupId>
+        <artifactId>spotless-maven-plugin</artifactId>
+        <version>${maven-plugin-spotless.version}</version>
+        <configuration>
+          <encoding>UTF-8</encoding>
+          <java>
+            <removeUnusedImports />
+            <importOrder>
+              <order>,\#</order>
+            </importOrder>
+            <endWithNewline />
+            <trimTrailingWhitespace />
+            <indent>
+              <spaces>true</spaces>
+              <spacesPerTab>4</spacesPerTab>
+            </indent>
+          </java>
+        </configuration>
+        <executions>
+          <execution>
+            <goals>
+              <goal>check</goal>
+            </goals>
+            <phase>process-sources</phase>
+          </execution>
+        </executions>
+      </plugin>
+    </plugins>
   </build>
 </project>

examples/maven-demo/src/main/java/info/jab/demo/EulerProblem01.java

@@ -5,10 +5,10 @@ public class EulerProblem01 implements IEuler<Integer, Integer> {
     /**
      * Multiples of 3 or 5
      * https://projecteuler.net/problem=1
-     * 
+     *
      * If we list all the natural numbers below 10 that are multiples of 3 or 5, we get 3,5,6 and 9. The sum of these multiples is 23.
      * Find the sum of all the multiples of 3 or 5 below the provided parameter.
-     * 
+     *
      * @param limit
      * @return
      */
@@ -25,4 +25,4 @@ public Integer solution(Integer limit) {
 
         return sum;
     }
-}
+}

examples/maven-demo/src/main/java/info/jab/demo/EulerProblem02.java

@@ -27,14 +27,14 @@ private static List<Long> fibonacci(Long limit) {
     /**
      * Even Fibonacci numbers
      * https://projecteuler.net/problem=2
-     * 
-     * Each new term in the Fibonacci sequence is generated by adding the previous two terms. 
+     *
+     * Each new term in the Fibonacci sequence is generated by adding the previous two terms.
      * By starting with 1 and 2, the first 10 terms will be:
      * 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, ...
-     * 
-     * By considering the terms in the Fibonacci sequence whose values do not exceed four million, 
+     *
+     * By considering the terms in the Fibonacci sequence whose values do not exceed four million,
      * find the sum of the even-valued terms.
-     * 
+     *
      * @param limit
      * @return
      */

examples/maven-demo/src/test/java/info/jab/demo/EulerProblem01Test.java

@@ -1,9 +1,9 @@
 package info.jab.demo;
 
-import static org.assertj.core.api.AssertionsForClassTypes.assertThat;
-
-import org.junit.jupiter.api.Test;
 import info.jab.demo.utils.EulerAnswersLoader;
+import org.junit.jupiter.api.Test;
+
+import static org.assertj.core.api.AssertionsForClassTypes.assertThat;
 
 class EulerProblem01Test {
 

examples/maven-demo/src/test/java/info/jab/demo/EulerProblem02Test.java

@@ -1,9 +1,9 @@
 package info.jab.demo;
 
-import static org.assertj.core.api.AssertionsForClassTypes.assertThat;
-
-import org.junit.jupiter.api.Test;
 import info.jab.demo.utils.EulerAnswersLoader;
+import org.junit.jupiter.api.Test;
+
+import static org.assertj.core.api.AssertionsForClassTypes.assertThat;
 
 public class EulerProblem02Test {