112-java-maven-plugins

Configure Maven plugins and profiles in pom.xml through guided questions.

423|90|Updated Feb 8, 2025

Search Tags:#configuration #plugins #java #maven #pom.xml #maven-plugin

Ready to run

npx skills add https://github.com/jabrena/cursor-rules-java --skill 112-java-maven-plugins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 112-java-maven-plugins
Source: https://github.com/jabrena/cursor-rules-java/tree/main/skills/112-java-maven-plugins
Command: npx skills add https://github.com/jabrena/cursor-rules-java --skill 112-java-maven-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Configures Maven plugins and profiles in pom.xml using a modular, question-driven process that preserves existing configuration.

Core Features & Use Cases

Modular, step-by-step approach to configuring plugins like enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd, OWASP, Spotless, Versions, and JMH.
Preserves and does not remove or replace existing plugins; reads references for detailed configurations and asks the user to confirm on conflicts.
Applies to Java projects using Maven and can tailor plugin sets based on project needs.
Optional components (scripts, references, assets) can be loaded on demand.

Quick Start

Begin by answering the guided questions to tailor Maven plugin changes to your project and apply only necessary plugins.

Frequently Asked Questions about 112-java-maven-plugins

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add Maven plugins to pom.xml without breaking existing build configuration?▼

To add Maven plugins without breaking existing builds, use a modular, question-driven process that reads references and applies only non-conflicting plugins to your pom.xml. The approach preserves current configurations and asks for user confirmation on any detected conflicts.

What is the best way to configure Java quality and security scanning tools in Maven?▼

The best way to configure Java quality and security scanning tools is through a step-by-step modular approach that adds plugins like SpotBugs, PMD, and OWASP to your pom.xml. This method tailors the plugin sets specifically to your project needs.

Do I need to run mvn validate before configuring Maven plugins in pom.xml?▼

Yes, you need to run mvn validate or ./mvnw validate before configuring Maven plugins in pom.xml. This prerequisite ensures your Java project environment is correctly set up and prevents build failures during the modular plugin application process.

Can I add version management and build information plugins to an existing Java Maven project?▼

Yes, you can add version management and build information plugins to an existing Java Maven project. The modular configuration process applies these plugins on demand while preserving and not replacing your current pom.xml setup.

Why does my Maven plugin configuration conflict with existing pom.xml properties?▼

Maven plugin configuration conflicts with existing pom.xml properties when overlapping settings are detected. The modular configuration process identifies these conflicts, preserves existing settings, and explicitly asks you to confirm changes before adding non-conflicting plugins.

How do I configure JMH and pitest plugins in a Java Maven project?▼

To configure JMH and pitest plugins in a Java Maven project, use a guided question-driven process that adds these testing plugins to your pom.xml. It ensures the configurations are tailored to your project and do not conflict with existing setups.