Fix some minor issues prior to potential release. - #752
Merged
Conversation
tisonkun
approved these changes
Aug 12, 2026
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
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.
The 4 key git.properties file added to the source-release.zip, are the same exact properties as in the binary, source and javadoc jar manifest.mf files.
This required a change in the pom.xml and in the src/assembly/source-release.xml files.
This ensures that one can exactly correlate the Apache released source to the jar files released to Maven Central
This is essentially ready for a 9.1.0 release, except that @freakyzoidberg wants to finish xorfilter he has been working on that only lacks some characterization testing.