build: remove legacy central-publishing-maven-plugin in favor of staging deployment#409
Open
AnshulPatni wants to merge 1 commit into
Conversation
…ing deployment Change-Id: I9191dd263f567d645eefd45a7e83dc4a390e02ee
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.
With the migration to staging-based release verification (
-DaltDeploymentRepository), retainingcentral-publishing-maven-plugin(extensions=true) inside project POMs caused deployment conflicts andNullPointerExceptionerrors (Server.clone() because server is null) when building non-snapshot release versions (v2.0.2).This cleanup removes the legacy direct-publishing plugin from all project modules, allowing standard
maven-deploy-pluginto cleanly stage GPG-signed release artifacts directly into the staging repository for automated promotion and verification.