Change from Maven to Github for publishing packages #371
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
56b6ef8 to
def2722
Compare
ettersi
reviewed
Sep 7, 2025
mchitre
approved these changes
Sep 8, 2025
0986fe0 to
651665c
Compare
Co-authored-by: Simon Etter <[email protected]>
Removed the release creation process from the README.
Document the release process for fjage.
651665c to
b88a3ab
Compare
ettersi
approved these changes
Sep 9, 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.
This PR moves the Gradle build process to move from Maven packages to Github package for publishing the fjage jar.
This will change the way fjage jar is consumed by using the
instead of