Repository navigation
fix(build): set Central deploymentName in bom module too - #2069
Merged
Merged
Conversation
The central-publishing-maven-plugin is declared in both the root POM and the bom module. The aggregated Central upload is performed by the bom module (last in the reactor), whose plugin configuration had no deploymentName, so the name configured in the root POM was dropped and the Central Portal showed the auto-generated 'Deployment <id>'. Add the same deploymentName to the bom module so the deployment is named cloud-security-services-integration-library-<version>.
kuntzed
approved these changes
Nov 6, 2026
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.
What
Set the Central
deploymentNamein thebommodule as well, so the aggregated Maven Central upload is actually named.Why
central-publishing-maven-pluginis declared twice (both in thereleaseprofile, bothextensions=true): once in the root POM and once inbom/pom.xml. The reactor performs a single aggregated upload, andbomis the last module in<modules>, so its plugin configuration is the one that takes effect for the upload. That configuration had nodeploymentName, so the name configured in the root POM was dropped and the Central Portal kept showing the auto-generatedDeployment <id>.Change
Add the same
deploymentNametobom/pom.xml:Notes
deploymentNameis applied at upload time and is not retroactive — the name shows up on the next publish, ascloud-security-services-integration-library-<version>.groupId:artifactId:version) are unaffected.