[Java] Fix fury benchmark jmh GPLV2 license conflict #1272
Merged
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
chaokunyang
force-pushed
the
fix_fury_benchmark_jmh_license
branch
2 times, most recently
from
bf39e59
to
61a3520
Compare
chaokunyang
force-pushed
the
fix_fury_benchmark_jmh_license
branch
from
ef9fdcc
to
729483e
Compare
PragmaTwice
approved these changes
Jan 2, 2024
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 closes #1271 by:
jmhprofile.According to apache license doc: https://www.apache.org/legal/resolved.html#optional
I believe GPLv2 license conflict has been addressed.