jabrena/plinth / skills/112-java-maven-plugins
112-java-maven-plugins
VerifiedUse when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins in pom.xml; Configure Maven quality plugins in pom.xml; Add Maven build lifecycle plugins for Java verification; Review Maven plugin versions and executions. Part of Plinth Toolkit
references/112-java-maven-plugins-profile-static-analysis.md
View on GitHub---
name: 112-java-maven-plugins-profile-static-analysis
description: Static analysis profile guidance for SpotBugs and PMD.
license: Apache-2.0
metadata:
author: Juan Antonio Breña Moral
version: 0.19.0
---
# Maven Plugins: pom.xml Configuration Best Practices
## Role
You are a Senior software engineer with extensive experience in Java software development.
## Tone
Treat the user as a knowledgeable partner. Preserve existing Maven configuration, explain trade-offs, and apply this reference only when the SKILL.md question flow selected this plugin or profile.
## Goal
Configure static analysis profile only when selected by the user in `112-java-maven-plugins`. Read this reference after the SKILL.md orchestration has validated the Maven project, analyzed existing plugins/properties/profiles, and collected the user's plugin/profile selections.
## Constraints
Apply only the selected static analysis profile configuration and preserve existing project configuration.
- Read this reference only when the user selected the corresponding Maven plugin or profile in the centralized question flow.
- Before adding configuration, check whether the plugin, property, reporting entry, support file, or profile already exists.
- Never remove or replace existing Maven configuration without explicit user confirmation.
- Add only the Maven properties, plugin configuration, profile configuration, and support files required by this reference.
## Steps
### Step 1: Add selected Maven properties
Add only the properties needed for this selected plugin/profile. If a property already exists, preserve the current value unless the user explicitly confirms a change.
```xml
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.version>3.9.10</maven.version>
<java.version>[USER_SELECTED_JAVA_VERSION]</java.version>
<maven-plugin-pmd.version>3.28.0</maven-plugin-pmd.version>
<maven-plugin-spotbugs.version>4.9.3.0</maven-plugin-spotbugs.version>
```
### Step 2: Static Code Analysis Profile Configuration
**Purpose**: Configure SpotBugs and PMD static analysis profile to detect potential bugs and code quality issues.
**Dependencies**: Only execute if user selected "Static code analysis (SpotBugs, PMD)" in the SKILL.md question flow. Requires completion of the SKILL.md orchestration steps and selected property handling.
**CRITICAL PRESERVATION RULE**: Only ADD this profile if it doesn't already exist. Never REPLACE or REMOVE existing profiles.
## Pre-Implementation Check
**BEFORE adding Static Analysis profile, check if it already exists in the pom.xml:**
If `<profiles>` section with `find-bugs` profile already exists: Ask user "Static analysis profile already exists. Do you want to enhance the existing configuration? (y/n)"
If user says "n": Skip this step entirely.
If user says "y": Proceed with adding missing configuration elements only.
**CONDITIONAL EXECUTION**: Only execute this step if user selected "Static code analysis (SpotBugs, PMD)" in the SKILL.md question flow.
## Static Analysis Profile Configuration
**ADD this profile to the `<profiles>` section in pom.xml ONLY if it doesn't already exist:**
```xml
<profile>
<id>find-bugs</id>
<activation>
<activeByDefault>false</activeByDefault>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>${maven-plugin-pmd.version}</version>
</plugin>
<plugin>
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
<version>${maven-plugin-spotbugs.version}</version>
<configuration>
<effort>Max</effort>
<threshold>Low</threshold>
<failOnError>true</failOnError>
</configuration>
</plugin>
</plugins>
</build>
<reporting>
<plugins>
<!-- SpotBugs reporting for Maven site -->
<plugin>
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
<version>${maven-plugin-spotbugs.version}</version>
<configuration>
<effort>Max</effort>
<threshold>Low</threshold>
<includeFilterFile>src/main/spotbugs/spotbugs-include.xml</includeFilterFile>
<excludeFilterFile>src/main/spotbugs/spotbugs-exclude.xml</excludeFilterFile>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
<version>${maven-plugin-pmd.version}</version>
</plugin>
</plugins>
</reporting>
</profile>
```
## Usage Examples
```bash
# Run static analysis
./mvnw clean verify -Pfind-bugs
# Generate reports
./mvnw site -Pfind-bugs
# View reports
open target/site/spotbugs.html
open target/site/pmd.html
```
## Validation
After adding this profile, verify the configuration:
```bash
# Test Static Analysis profile
./mvnw clean verify -Pfind-bugs
```
#### Step Constraints
- **MUST** only add Static Analysis profile if static analysis was selected in the SKILL.md question flow
- **MUST** check if profile already exists before adding
- **MUST** ask user permission before modifying existing profile configuration
- **MUST** use selected version properties for plugin versions
- **MUST** skip this step entirely if static analysis was not selectedRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |