fix(maven): name the central deployment after its coordinates - #654
Merged
Conversation
The plugin's default deployment name is the literal "Deployment", so the portal listed the jar and the AAR as one named upload and one anonymous one. The AAR's plugin builds `group-artifactId-version` for itself; this is the same shape. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YSePnR4Jcj5cq3H1D11xcd
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
1 participant
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.
In the Central Portal, the
odr-core-javaupload showed up as Deployment while the AAR showed up asapp.opendocument-odr-core-android-6.2.0— so of the two deployments awaiting a manual release, only one said what it was.central-publishing-maven-plugindeclares its default as the literal string:and
jni/pom.xmlnever overrode it.The AAR gets a real name because vanniktech's plugin builds one. Its
MavenCentralBuildServiceconcatenates group, artifactId and version with the recipe\1-\1-\1— hyphens, not colons, which is why this uses that separator rather than the more usualgroup:artifact:version.Verified
mvn help:effective-pom -Pcentral -Drevision=6.2.0resolves it, confirming${project.version}reaches through the CI-friendly${revision}indirection:against the AAR's
app.opendocument-odr-core-android-6.2.0.Cosmetic — it changes the portal label only, not coordinates, artifacts or the published pom. Takes effect on the next release; v6.2.0 is already out.
🤖 Generated with Claude Code