Repository navigation
ci(java): central-publishing-maven-plugin 0.12.0, so the bundle has only the artifact files - #61
Merged
Merged
Conversation
…nly the artifact files The sai-sdk-java-v0.1.0 deployment failed on Central: "Bundle has content that does NOT have a .pom file: ai/simular/sai-sdk". 0.7.0 staged Maven's maven-metadata-local.xml and _remote.repositories into the bundle; 0.12.0 leaves them out. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
The
sai-sdk-java-v0.1.0publish (run) built, tested, signed and uploaded, then Central rejected the deployment:Building the bundle locally with 0.7.0 (
-DskipPublishing) shows why: next to0.1.0/…it containsai/simular/sai-sdk/maven-metadata-local.xmland0.1.0/_remote.repositories*, which Maven's local-install step writes. 0.12.0 knows both names and leaves them out of the bundle (they're in its classes; 0.7.0 only knewmaven-metadata-central-staging.xml). Same configuration otherwise.Nothing was published, so
0.1.0is still free on Central. Once this merges, the Java release goes out again (re-tag 0.1.0 on the new main, or bump to 0.1.1).🤖 Generated with Claude Code