Migrate from Nexus Staging to Central Publishing Maven plugin #463
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.
This pull request updates the Maven publishing configuration across all modules to use the new Central Repository publishing endpoints and plugin. It replaces the deprecated Sonatype Nexus Staging plugin and AWS-specific endpoints with the new
central-publishing-maven-pluginand updated URLs, ensuring compatibility with the latest publishing requirements.Repository publishing configuration updates:
<distributionManagement>section in allpom.xmlfiles to use the new Central Repository (central) IDs and endpoints for both snapshot and release repositories, replacing the oldossrhand AWS URLs. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]Build and deployment plugin updates:
nexus-staging-maven-pluginwith the newcentral-publishing-maven-plugin(version 0.7.0) in all modules, and updated the plugin configuration to usepublishingServerId=central. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]Dependency cleanup:
commons-compressin the rootpom.xml, as it is no longer required for vulnerability mitigation. Additionally the new publishing plugins required removal of that block.