HBX-2985 Use JReleaser to publish artifacts #5123
Closed
Conversation
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
|
Just tested it this morning with @dreab8 and all seems ok. |
|
The PR was rebased and merged (and successfully used in a release). So I will close the PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
https://hibernate.atlassian.net/browse/HBX-2985
Openign as a draft for now... this is what @dreab8 and I had done so far. there's one thing we should double check with the jreleaser signing, but other than that it should be all that is needed to switch to the updated scripts.
btw... you'll notice the difference that now we do not need maven to attach gradle artifacts to its build as gradle build will publish all it needs to a local staging dir that is then later used by Jreleaser to publish to nexus.