Repository navigation
GH-3894: [1.19.x] Stage releases through nexus-staging-maven-plugin - #3910
Closed
RussellSpitzer wants to merge 1 commit into
Closed
RussellSpitzer wants to merge 1 commit into
RussellSpitzer wants to merge 1 commit into
Conversation
…ugin Backports the pom.xml part of the master change. The release workflows run the scripts from master but build the release branch's pom, so a 1.19.x patch RC staged by the new prepare-rc.sh needs the plugin in this branch's apache-release profile. Without it, mvn deploy falls back to maven-deploy-plugin, Nexus implicitly creates an open repository, and prepare-rc.sh fails after the deploy because no staging repository ID was recorded. Only pom.xml changes; the release scripts are not on this branch. The existing build-helper and exec plugin versions on 1.19.x are kept. Generated-by: Claude Opus 5.5 (1M context)
Contributor
|
Do we need to backport to the 1.19.x branch already? For the 1.19.0 release I would suggest dropping and re-creating the branch |
Member
Author
|
I had thought we already did a 1.19 release, we don't need to backport if we haven't yet. so we can close this. |
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.
Backports the pom.xml part of the master change. The release workflows run the scripts from master but build the release branch's pom, so a 1.19.x patch RC staged by the new prepare-rc.sh needs the plugin in this branch's apache-release profile. Without it, mvn deploy falls back to maven-deploy-plugin, Nexus implicitly creates an open repository, and prepare-rc.sh fails after the deploy because no staging repository ID was recorded.
Only pom.xml changes; the release scripts are not on this branch. The existing build-helper and exec plugin versions on 1.19.x are kept.
Generated-by: Claude Opus 5.5 (1M context)