Remove relocation stub from active reactor + repo-wide URL cleanup#149
Merged
Merged
Conversation
…eanup
The relocation stub (net.ladenthin:llamacpp-ai-index-maven-plugin) was
published once at 1.0.4 as part of the 1.1.1 release, and the redirect
was verified working end-to-end: a Maven resolution of the old
coordinates from a completely clean local repository correctly follows
the relocation through to srcmorph-maven-plugin:1.1.1 and its full
dependency graph. The published artifact is permanent on Maven Central
regardless of this repo's module list, and it will never need another
release, so there's no reason to keep carrying it (and the
`versions:set -Dexcludes=...` footgun it required) in active
development.
- Removed llamacpp-ai-index-maven-plugin/ and its <module> entry from
the root pom.
- Updated CLAUDE.md, README.md, TODO.md, CHANGELOG.md, docs/RELEASE.md,
srcmorph-maven-plugin/README.md to reflect the 3-module reactor and
the stub's now-historical status; removed the now-moot versions:set
exclusion caveat from TODO.md and CLAUDE.md.
- .github/workflows/publish.yml comment updated (no functional change
needed - the stub never produced a jar, so no per-module CI step
ever referenced it beyond the aggregate reactor build).
- Fixed a real staleness bug found along the way: srcmorph's own
spotbugs-exclude.xml comments still called the sibling plugin module
by its pre-rename name ("llamacpp-ai-index-maven-plugin module")
instead of "srcmorph-maven-plugin module" - missed during the
original Step 9 rename.
- Repo-wide GitHub link cleanup: renamed bernardladenthin/llamacpp-ai-index-maven-plugin
URLs to the canonical bernardladenthin/srcmorph in README.md,
CONTRIBUTING.md, SECURITY.md, SUPPORT.md, .github/ISSUE_TEMPLATE/config.yml,
and REUSE.toml's package metadata. Left third-party service-specific
identifiers untouched (SonarCloud project key, Snyk/FOSSA/Libraries.io/
Scorecard/REUSE.software badges) since those may be registered under
the old name independently of the GitHub repo and I can't verify
whether they were updated. Updated the README's Maven Central +
Snapshot badges to point at srcmorph-maven-plugin (the real, current
plugin artifact) instead of the now-deprecated stub coordinates.
Verified: mvn clean verify - BUILD SUCCESS. Reactor build order confirmed
as 4 projects (parent + 3 real modules), no stub.
bernardladenthin
had a problem deploying
to
maven-central
July 16, 2026 08:22 — with
GitHub Actions
Failure
bernardladenthin
temporarily deployed
to
startgate
July 16, 2026 08:22 — with
GitHub Actions
Inactive
bernardladenthin
had a problem deploying
to
maven-central
July 16, 2026 08:22 — with
GitHub Actions
Failure
Coverage Report for CI Build 29483214795Coverage remained the same at 90.779%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
net.ladenthin:llamacpp-ai-index-maven-plugin) from the active reactor. It was published once at1.0.4as part of the1.1.1release, and the redirect was verified working end-to-end — a Maven resolution of the old coordinates from a completely clean local repository correctly follows the relocation through tosrcmorph-maven-plugin:1.1.1and its full dependency graph. The published artifact is permanent on Maven Central regardless of this repo's module list and will never need another release, so there's no reason to keep carrying it (and theversions:set -Dexcludes=...footgun it required) in active development.CLAUDE.md,README.md,TODO.md,CHANGELOG.md,docs/RELEASE.md,srcmorph-maven-plugin/README.mdto reflect the 3-module reactor and the stub's now-historical status..github/workflows/publish.ymlcomment updated (no functional change needed — the stub never produced a jar, so no per-module CI step ever referenced it beyond the aggregate reactor build).srcmorph's ownspotbugs-exclude.xmlcomments still referred to the sibling plugin module by its pre-rename name (llamacpp-ai-index-maven-plugin module) instead ofsrcmorph-maven-plugin module— missed during the original Step 9 rename.bernardladenthin/llamacpp-ai-index-maven-pluginURLs to the canonicalbernardladenthin/srcmorphinREADME.md,CONTRIBUTING.md,SECURITY.md,SUPPORT.md,.github/ISSUE_TEMPLATE/config.yml, andREUSE.toml's package metadata. Left third-party service-specific identifiers untouched (SonarCloud project key, Snyk/FOSSA/Libraries.io/Scorecard/REUSE.software badges) since those may be registered under the old name independently of the GitHub repo and can't be verified from here. Updated the README's Maven Central + Snapshot badges to point atsrcmorph-maven-plugin(the real, current plugin artifact) instead of the now-deprecated stub coordinates.Test plan
mvn clean verifyfrom repo root — BUILD SUCCESSCHANGELOG.md/module READMEs left as accurate history; historical benchmark output files indocs/ai-index-benchmark/deliberately untouched, consistent with existing precedent)Related issues / PRs
Follow-up to #144–#148 — closes out the relocation-stub lifecycle after confirming the redirect works.
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdGenerated by Claude Code