112-java-maven-plugins

# Maven Plugins: pom.xml Configuration Best Practices Configure Maven plugins and profiles in pom.xml using a structured, question-driven process that preserves existing configuration. **This is an interactive SKILL**. **What is covered in this Skill?** Maven plugins: - Maven Compiler - Maven Enforcer - Maven Surefire - Maven Failsafe - HTML test reports (Surefire Report, JXR) - Maven Spotless - Maven Flatten - Maven Versions - Maven Git Commit ID - Maven Jib Maven profiles: - JaCoCo (code coverage) - PiTest (mutation testing) - Security (OWASP dependency check) - Static analysis (SpotBugs, PMD) - SonarQube/SonarCloud - JMH (Java Microbenchmark Harness) - Cyclomatic complexity ## Constraints Before applying plugin recommendations, ensure the project is in a valid state. Use a structured, question-driven process that preserves existing configuration and adds only what the user selects. - **MANDATORY**: Run `./mvnw validate` or `mvn validate` before applying any plugin recommendations - **SAFETY**: If validation fails, stop and ask the user to fix issues—do not proceed until resolved - **SCOPE**: Begin with Step 1 (existing configuration analysis) before any changes. Never remove or replace existing plugins; only add new ones that do not conflict - **BEFORE READING PLUGIN REFERENCES**: Run the question flow embedded in this SKILL.md first. Ask questions one-by-one in strict order, collect all selected plugins/profiles and conditional values, then read only the implemen...