원클릭으로 Manus에서 모든 스킬 실행

112-java-maven-plugins

스타0

포크2

업데이트2026년 3월 19일 20:26

Use 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. Part of the skills-for-java project

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

jabrena

jabrena/cursor-rules-examples

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

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 APPLYING: Read the reference for detailed plugin configurations, XML templates, and constraints for each step

When to use this skill

Configure Maven plugins in pom.xml
Add Maven plugins to pom.xml
Improve Maven plugins configuration in pom.xml

Reference

For detailed guidance, examples, and constraints, see references/112-java-maven-plugins.md.

이 저장소의 다른 Skills

같은 저장소

014-agile-create-user-story

jabrena/cursor-rules-examples

Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. Part of the skills-for-java project

2026-03-190

020-planning-enhance-ai-plan-mode

jabrena/cursor-rules-examples

Use when creating a plan using Plan model and enhancing structured design plans in Cursor Plan mode for Java implementations. Use when the user wants to create a plan, design an implementation, structure a development plan, or use plan mode for outside-in TDD, feature implementation, or refactoring work. Part of the skills-for-java project

2026-03-190

030-architecture-adr-general

jabrena/cursor-rules-examples

Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. Part of the skills-for-java project

2026-03-190

031-architecture-adr-functional-requirements

jabrena/cursor-rules-examples

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. Part of the skills-for-java project

2026-03-190

032-architecture-adr-non-functional-requirements

jabrena/cursor-rules-examples

Facilitates conversational discovery to create Architectural Decision Records (ADRs) for non-functional requirements using the ISO/IEC 25010:2023 quality model. Use when the user wants to document quality attributes, NFR decisions, security/performance/scalability architecture, or design systems with measurable quality criteria. Part of the skills-for-java project

2026-03-190

033-architecture-diagrams

jabrena/cursor-rules-examples

Use when you need to generate Java project diagrams — including UML sequence diagrams, UML class diagrams, C4 model diagrams, UML state machine diagrams, and ER (Entity Relationship) diagrams — through a modular, step-based interactive process that adapts to your specific visualization needs. Part of the skills-for-java project

2026-03-190

name	112-java-maven-plugins
description	Use 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. Part of the skills-for-java project
license	Apache-2.0
metadata	{"author":"Juan Antonio Breña Moral","version":"0.13.0-SNAPSHOT"}

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 APPLYING: Read the reference for detailed plugin configurations, XML templates, and constraints for each step

When to use this skill

Configure Maven plugins in pom.xml
Add Maven plugins to pom.xml
Improve Maven plugins configuration in pom.xml

Reference

For detailed guidance, examples, and constraints, see references/112-java-maven-plugins.md.