Switch java client project to use Maven instead of Gradle #98
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
zack13532
force-pushed
the
07-17-requestoptions
branch
from
75d3613 to
d734c33
Compare
zack13532
force-pushed
the
07-17-requestoptions
branch
8 times, most recently
from
2bd0c6c to
890e2f6
Compare
zack13532
force-pushed
the
07-17-requestoptions
branch
from
890e2f6 to
bb51cd3
Compare
zack13532
changed the title
sanikan1
approved these changes
Jul 24, 2025
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.
We use to publish new versions of the client on OSSRH, but that has been turned down in favor of Maven Central Repository. And there's basically only support for automated publishing via its Maven plugin - I couldn't get it to work with Gradle. So this switches over all build, test, signing, and publishing tasks to be configured with Maven, deleting the Gradle counterparts. Also updates the GH Actions appropriately. Verified that the Publish snapshot action works, which shows that the new Maven setup can build, sign, and publish appropriately. After we get some approval from customers (signifyd in particular) that the published snapshot version works, we can run the release and confirm that it works.