This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
chore: nexus-publish plugin cannot publish multi-module project to maven central #1512
Conversation
This file contains 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
google-cla
bot
added
the
cla: yes
Neenu1995
changed the title
suztomo
approved these changes
Oct 13, 2021
Neenu1995
added
the
automerge
gcf-merge-on-green
bot
removed
the
automerge
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Until this issue is resolved, gax cannot use nexus-publish to publish to maven central because the plugin do not persist stagingProfile information between command runs. Thus both the staging command and publish command has to be run in a single command. But, since gax has multiple modules(each modules gets staged in separate run) this is not a workable approach.
So currently, the library gets staged to sonatype. Publish it manually from there(Get permission to publish if you frequently publish gax-java or @Neenu1995 can publish). A possible move to maven pom might be a better solution also.