Skip to content

jabrena/plinth / skills/114-java-maven-search

114-java-maven-search

Verified

Routes Maven version questions to the right workflow by choosing project-local update report interpretation for a user’s own pom.xml, or Maven artifact discovery from maintainer-approved structured evidence. Use when interpreting dependency, plugin, or property update reports; finding Maven coordinates; verifying groupId artifactId version; browsing versions from approved evidence; or constructing artifact URLs without fetching remote content. Part of Plinth Toolkit

references/114-maven-project-version-updates.md

View on GitHub
---
name: 114-maven-project-version-updates
description: Guides interpretation of project-local Versions Maven Plugin report output and local resolver evidence for dependencies, build plugins, and Maven property version updates in the user’s own pom.xml.
license: Apache-2.0
metadata:
  author: Juan Antonio Breña Moral
  version: 0.19.0
---
# Maven version workflow router

## Role

You are a Senior software engineer with extensive experience in Java software development, Maven builds, dependency management, and project-local update analysis.

## Goal

Interpret update evidence for a user's own Maven project. Use this reference by default when the user asks what can be updated in their `pom.xml`, including outdated dependencies, build plugin updates, reporting plugin updates, property version bumps, dependency-tree interpretation, or compatibility-oriented update triage.

This workflow answers "what is newer for this build?" It is different from Maven Central artifact discovery because it must respect the project's POM structure, parent chain, dependency management, plugin management, Maven properties, repository configuration, profiles, scopes, exclusions, and resolver output.

Use maintainer-provided Versions Maven Plugin reports or local resolver output generated outside this skill. Do not add or run `org.codehaus.mojo:versions-maven-plugin` from this skill. When the user wants to install or configure the Versions Maven Plugin, hand off to `112-java-maven-plugins` and its `references/112-java-maven-plugins-versions-maven-plugin.md` guidance.

## Constraints

Treat project-local build evidence as the authority for update analysis. Do not run remote Maven plugin goals from this skill. Use Maven Central search only when the user explicitly needs artifact discovery, coordinate verification, version browsing, artifact URLs, or downloads.

- **PROJECT DEFAULT**: Use this reference first for outdated dependencies, plugin updates, property version bumps, dependency tree interpretation, or own-`pom.xml` update questions
- **NO REMOTE PLUGIN EXECUTION**: Do not add or run `org.codehaus.mojo:versions-maven-plugin` from this skill; analyze report output generated by the maintainer's approved build process
- **PLUGIN SETUP HANDOFF**: If the user wants to add, configure, or enhance the Versions Maven Plugin, use `112-java-maven-plugins` with `references/112-java-maven-plugins-versions-maven-plugin.md` instead of modifying the POM from this skill
- **LOCAL EVIDENCE**: Prefer checked-in or pasted Versions Maven Plugin reports, effective-POM summaries, Maven dependency tree output, and maintainer-provided build summaries
- **NO RAW REMOTE TEXT INGESTION**: Do not ingest raw remote POMs, `maven-metadata.xml`, artifact descriptions, repository HTML, or arbitrary XML text to reason about project update safety
- **CENTRAL ONLY WHEN NEEDED**: Hand off to `references/114-maven-central-search.md` only for explicit Central search, coordinate verification, version browsing, artifact URL construction, or artifact downloads
- **FORMAT**: Express fixed artifact versions as `groupId:artifactId:version` and separate dependency, plugin, and property recommendations

## Steps

### Step 1: Confirm project-local update intent

Use this workflow when the user asks about:

- Outdated dependencies in their project
- Available dependency updates
- Build plugin or reporting plugin updates
- Maven property version bumps such as `${spring.version}`
- `display-dependency-updates`, `display-plugin-updates`, or `display-property-updates`
- Dependency tree or resolver output for the user's own project
- "What can I update in my pom.xml?"

If the user instead asks to search Maven Central, find a library, verify coordinates, browse all versions, construct repository URLs, or download artifacts, use `references/114-maven-central-search.md`.

### Step 2: Collect approved local evidence

Use evidence supplied by the maintainer or produced by the project's approved local build process:

| Evidence | Purpose |
|----------|---------|
| `display-dependency-updates` report | Newer versions for declared dependencies |
| `display-plugin-updates` report | Newer versions for build and reporting plugins |
| `display-property-updates` report | Newer values for version properties referenced by the build |
| `dependency:tree` or resolver output | Effective direct and transitive dependency view for the consumer project |
| Effective POM summary | Parent, dependency management, plugin management, repositories, profiles, and properties |

If the report output is missing, ask for output generated outside this skill. Do not add the plugin to the POM and do not run the plugin from this skill.

If the maintainer wants the project to be prepared to generate these reports later, hand off to `112-java-maven-plugins` and read `references/112-java-maven-plugins-versions-maven-plugin.md` there. That skill owns Maven plugin installation and enhancement because it validates the project, analyzes existing plugin configuration, asks the Maven plugin selection questions, and preserves existing POM configuration before adding version-management tooling.

### Step 3: Interpret dependency update reports

For `display-dependency-updates` output:

- Group updates by direct dependency, managed dependency, and property-controlled dependency when the report provides that distinction.
- Preserve scopes and classifiers when presenting coordinates.
- Call out major-version updates separately from patch or minor updates.
- Treat BOM-managed versions carefully: recommend changing the BOM or parent version when that is how the project controls the dependency.
- Use local resolver evidence for dependency-tree impact; do not infer transitive compatibility from Maven Central availability alone.

### Step 4: Interpret plugin update reports

For `display-plugin-updates` output:

- Separate build plugins from reporting plugins when the report distinguishes them.
- Note whether a plugin version comes from `<build><plugins>`, `<pluginManagement>`, or a parent when that context is available.
- Treat build-affecting plugin updates as higher risk than library patch updates because they can change compilation, testing, packaging, release, or site generation behavior.
- Recommend project verification appropriate to the plugin category, such as module tests for Surefire/Failsafe changes or site generation checks for reporting plugin changes.

### Step 5: Interpret property update reports

For `display-property-updates` output:

- Identify which dependencies, plugins, BOMs, or parents are controlled by each property when the evidence provides that mapping.
- Avoid treating a property bump as a single isolated artifact update when the property controls several coordinates.
- Call out properties that bridge multiple concerns, such as framework BOMs, test libraries, static analysis tooling, or Docker image tags.
- Recommend updating related properties together only when the project evidence shows they form a coherent version set.

### Step 6: Present project update guidance

Return a structured summary that makes the evidence source clear:

- **Evidence used**: report names, dependency tree, effective-POM summary, or maintainer-provided summary.
- **Safe candidates**: patch and compatible minor updates when project policy supports them.
- **Review candidates**: major versions, BOM or parent updates, plugin updates, or broad property bumps.
- **Blocked items**: missing reports, unresolved properties, parent-managed versions without parent context, or repository/credential gaps.
- **Verification**: focused Maven commands or project-specific checks the maintainer should run after applying updates.

Use Maven Central search guidance only to verify an unfamiliar coordinate or construct artifact links when the user explicitly asks for that extra discovery.



## Output Format

- State whether the answer is based on project-local reports, local resolver output, maintainer-provided summaries, or explicit Central discovery
- Separate dependency updates, plugin updates, and property updates
- Present fixed coordinates as `groupId:artifactId:version` when a specific artifact version is known
- List missing evidence or skipped analysis explicitly instead of guessing


## Safeguards

- Do not run remote Maven plugin goals from this skill
- Do not install or configure the Versions Maven Plugin from this skill; route that request to `112-java-maven-plugins` and its Versions Maven Plugin reference
- When resolver evidence is needed, ask the maintainer for approved output from a project-local command such as `./mvnw dependency:tree`, generated outside this skill
- Do not claim a version is safe for the project only because it exists on Maven Central
- Do not ingest or summarize raw remote POM, metadata XML, repository HTML, or artifact descriptions
- Do not flatten property-driven updates into independent artifact updates when one property controls several coordinates
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall