MINOR: Bump version of grgit to 4.1.1 #11561
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
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1.
|
Call for review: @ijuma @lbradstreet |
juha-aiven
added a commit
to aiven/kafka
that referenced
this pull request
Dec 9, 2021
Explanation in apache#11561. That PR cannot be merged in 2.8 branch without conflicts.
cadonna
added a commit
that referenced
this pull request
Dec 9, 2021
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
|
Cherry-picked to 3.1 \cc @dajac |
cadonna
added a commit
that referenced
this pull request
Dec 9, 2021
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
|
Cherry-picked to 3.0 |
juha-aiven
added a commit
to aiven/kafka
that referenced
this pull request
Dec 9, 2021
Explanation in apache#11561. That PR cannot be merged in 2.8 branch without conflicts.
juha-aiven
added a commit
to aiven/kafka
that referenced
this pull request
Dec 9, 2021
Explanation in apache#11561. That PR cannot be merged in 2.7 branch without conflicts.
juha-aiven
added a commit
to aiven/kafka
that referenced
this pull request
Dec 9, 2021
Explanation in apache#11561. That PR cannot be merged in 2.7 branch without conflicts.
3 tasks
3 tasks
xdgrulez
pushed a commit
to xdgrulez/kafka
that referenced
this pull request
Dec 22, 2021
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
kamalcph
pushed a commit
to satishd/kafka
that referenced
this pull request
Jan 12, 2022
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
lmr3796
pushed a commit
to lmr3796/kafka
that referenced
this pull request
Jan 12, 2022
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
nateab
pushed a commit
to confluentinc/kafka
that referenced
this pull request
Jan 12, 2022
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
lmr3796
added a commit
to linkedin/kafka
that referenced
this pull request
Jan 13, 2022
…#244) grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org> Co-authored-by: Bruno Cadonna <bruno@confluent.io>
divijvaidya
pushed a commit
to Hangleton/kafka
that referenced
this pull request
Apr 28, 2022
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
lmr3796
pushed a commit
to lmr3796/kafka
that referenced
this pull request
Jun 2, 2022
grgit 4.1.0 caused unsupported version error during gradle builds. The reason was that grgit 4.1.0 uses always the latest JGit version internally. Unfortunately, the latest JGit version was compiled with a Java version later than Java 8 which caused the unsupported version error during gradle builds for Java 8. grgit 4.1.1 fixed this issue by upper bounding the version of JGrit to a version that is still compiled with Java 8. Consequently, we can remove the hotfix we merged in commit d1e0d2b and instead bump the grgit version from 4.1.0 to 4.1.1. Reviewer: John Roesler <vvcephei@apache.org>
2 tasks
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.
grgit 4.1.0 caused unsupported version error during gradle builds.
The reason was that grgit 4.1.0 uses always the latest JGit version
internally. Unfortunately, the latest JGit version was compiled with
a Java version later than Java 8 which caused the unsupported version
error during gradle builds for Java 8.
grgit 4.1.1 fixed this issue by upper bounding the version of JGrit
to a version that is still compiled with Java 8. Consequently, we can
remove the hotfix we merged in PR #11554
and instead bump the grgit version from 4.1.0 to 4.1.1.
Committer Checklist (excluded from commit message)