Maven Central search and coordinates
Help users search Maven Central, resolve groupId:artifactId:version, read version history, and build correct download URLs; and when working on their project, verify versions-maven-plugin and run versions:display-* goals for dependency, plugin, and property updates. What is covered:
- Maven Central Search API — e.g. keyword search for Spring Boot starters (
spring-boot-starter) or coordinate filters (g:org.springframework.boot AND a:spring-boot-starter-parent)
- Direct repository layout and
maven-metadata.xml
- POM, JAR,
-sources.jar, -javadoc.jar URL patterns
- Parsing POMs for direct dependencies; transitive trees via Maven/Gradle on the consumer project
- Versions Maven Plugin — ensure
org.codehaus.mojo:versions-maven-plugin is declared, then ./mvnw versions:display-property-updates, versions:display-dependency-updates, versions:display-plugin-updates
- Output format: structured coordinates, tables, and verifiable HTTPS links
Constraints
Verify coordinates against the Search API or repository responses before asserting availability. Prefer release versions unless snapshots are explicitly required.
- VERIFY: Do not invent GAVs — confirm via Search API or successful GET of metadata/POM
- FORMAT: Always express full coordinates as
groupId:artifactId:version when a version is fixed
- BEFORE APPLYING: Read the reference for step-by-step workflows, query syntax, and URL patterns
- EDGE CASE: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
- EDGE CASE: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
- EDGE CASE: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off
When to use this skill
- Search Maven Central
- Find Maven dependency
- Maven coordinates
- groupId artifactId version
- Latest version Maven
- maven-metadata.xml
- Download JAR from Maven Central
- Download javadocs
- Dependency tree transitive
- display-dependency-updates
- display-plugin-updates
- Outdated Maven dependencies
Workflow
- Read Maven search reference workflow
Read references/114-java-maven-search.md before forming queries, coordinate checks, or URL outputs.
- Perform Maven Central discovery and verification
Use Search API and repository metadata/POM checks to confirm valid coordinates and available versions.
- Format results with full coordinates and links
Return groupId:artifactId:version outputs, structured tables, and verifiable HTTPS artifact URLs.
- Run project-local update checks when applicable
When working on a local project, ensure versions-maven-plugin usage and run versions:display-* reports for properties, dependencies, and plugins.
Reference
For detailed guidance, examples, and constraints, see references/114-java-maven-search.md.
1---2name: 114-java-maven-search3description: Covers Maven Central search (Search API, maven-metadata.xml, artifact URLs) and project-local update reports via versions-maven-plugin (display-property-updates, display-dependency-updates, display-plugin-updates). Use when finding or verifying coordinates, browsing Central, or checking what newer versions apply to the user’s pom.xml. This should trigger for requests such as Search Maven Central; Find Maven dependency; Maven coordinates; groupId artifactId version. Part of cursor-rules-java project4license: Apache-2.05---6# Maven Central search and coordinates
7
8Help users search Maven Central, resolve **groupId:artifactId:version**, read version history, and build correct download URLs; and when working on **their** project, verify `versions-maven-plugin` and run `versions:display-*` goals for dependency, plugin, and property updates. **What is covered:**
9
10- Maven Central Search API — e.g. keyword search for Spring Boot starters (`spring-boot-starter`) or coordinate filters (`g:org.springframework.boot AND a:spring-boot-starter-parent`)
11- Direct repository layout and `maven-metadata.xml`
12- POM, JAR, `-sources.jar`, `-javadoc.jar` URL patterns
13- Parsing POMs for direct dependencies; transitive trees via Maven/Gradle on the consumer project
14- Versions Maven Plugin — ensure `org.codehaus.mojo:versions-maven-plugin` is declared, then `./mvnw versions:display-property-updates`, `versions:display-dependency-updates`, `versions:display-plugin-updates`
15- Output format: structured coordinates, tables, and verifiable HTTPS links
16
17## Constraints
18
19Verify coordinates against the Search API or repository responses before asserting availability. Prefer release versions unless snapshots are explicitly required.
20
21- **VERIFY**: Do not invent GAVs — confirm via Search API or successful GET of metadata/POM
22- **FORMAT**: Always express full coordinates as `groupId:artifactId:version` when a version is fixed
23- **BEFORE APPLYING**: Read the reference for step-by-step workflows, query syntax, and URL patterns
24- **EDGE CASE**: If the user goal is ambiguous, stop and ask a clarifying question before editing files or running project-wide commands
25- **EDGE CASE**: If required context, files, credentials, or tools are missing, report the blocker explicitly and ask whether to proceed with setup or fallback guidance
26- **EDGE CASE**: If requested changes conflict with project constraints or safety boundaries, explain the conflict and ask for user confirmation on the preferred trade-off
27
28## When to use this skill
29
30- Search Maven Central
31- Find Maven dependency
32- Maven coordinates
33- groupId artifactId version
34- Latest version Maven
35- maven-metadata.xml
36- Download JAR from Maven Central
37- Download javadocs
38- Dependency tree transitive
39- display-dependency-updates
40- display-plugin-updates
41- Outdated Maven dependencies
42
43## Workflow
44
451. **Read Maven search reference workflow**
46
47Read `references/114-java-maven-search.md` before forming queries, coordinate checks, or URL outputs.
48
492. **Perform Maven Central discovery and verification**
50
51Use Search API and repository metadata/POM checks to confirm valid coordinates and available versions.
52
533. **Format results with full coordinates and links**
54
55Return `groupId:artifactId:version` outputs, structured tables, and verifiable HTTPS artifact URLs.
56
574. **Run project-local update checks when applicable**
58
59When working on a local project, ensure versions-maven-plugin usage and run `versions:display-*` reports for properties, dependencies, and plugins.
60
61## Reference
62
63For detailed guidance, examples, and constraints, see [references/114-java-maven-search.md](references/114-java-maven-search.md).