Maven SNAPSHOT Publication Recovery

Overview

Recover incomplete Maven SNAPSHOT publication by proving the failure from an isolated consumer, classifying the first unresolved coordinate, backfilling only verified gaps, and repeating the consumer probe until the dependency graph closes.

The core rule is: publication is not proven by a successful local build or upload; it is proven by remote resolution from a new Maven local repository.

Use maven-release-validation for planned release readiness and normal end-to-end publication. Use this skill after publication has become inconsistent or a fresh consumer exposes a missing remote dependency graph.

Quick Start

Use this skill for requests such as:

• “这个 SNAPSHOT 已上传，但新机器还是解析失败，帮我恢复发布。”
• “用空缓存验证所有维护分支，只补齐缺失制品。”
• “Maven 4 deploy 被仓库 401 阻断，安全地改用 Maven 3 回填。”

Before any remote mutation, inspect the real Git root, branch, dirty state, POM hierarchy, repository settings, required JDK/Maven matrix, and any existing verification script. Do not switch branches, publish, or overwrite artifacts without the authorization already implied or explicitly given by the user.