[KYUUBI #6747] Bump Guava from 32.1.3 to 33.3.1
# 🔍 Description ## Issue References 🔗 This pull request fixes # ## Describe Your Solution 🔧 - Bump guava from 32.1.3 (Oct 11, 2023) to 33.3.1 (Sep 23, 2024 ) : https://github.com/google/guava/releases/tag/v33.3.1 ## Types of changes 🔖 - [ ] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ## Test Plan 🧪 #### Behavior Without This Pull Request ⚰️ #### Behavior With This Pull Request 🎉 #### Related Unit Tests --- # Checklist 📝 - [ ] This patch was not authored or co-authored using [Generative Tooling](https://www.apache.org/legal/generative-tooling.html) **Be nice. Be informative.** Closes #6747 from bowenliang123/guava-33.3.1. Closes #6747 39abf1b23 [Bowen Liang] bump guava from 32.1.3 to 33.3.1 Authored-by: Bowen Liang <liangbowen@gf.com.cn> Signed-off-by: Bowen Liang <liangbowen@gf.com.cn>
This commit is contained in:
parent
04468a60c9
commit
a1a5a9d27f
@ -46,7 +46,7 @@ grpc-protobuf/1.65.1//grpc-protobuf-1.65.1.jar
|
||||
grpc-stub/1.65.1//grpc-stub-1.65.1.jar
|
||||
grpc-util/1.65.1//grpc-util-1.65.1.jar
|
||||
gson/2.10.1//gson-2.10.1.jar
|
||||
guava/32.1.3-jre//guava-32.1.3-jre.jar
|
||||
guava/33.3.1-jre//guava-33.3.1-jre.jar
|
||||
hadoop-client-api/3.3.6//hadoop-client-api-3.3.6.jar
|
||||
hadoop-client-runtime/3.3.6//hadoop-client-runtime-3.3.6.jar
|
||||
hk2-api/2.6.1//hk2-api-2.6.1.jar
|
||||
|
||||
2
pom.xml
2
pom.xml
@ -145,7 +145,7 @@
|
||||
<flink.archive.download.skip>false</flink.archive.download.skip>
|
||||
<google.jsr305.version>3.0.2</google.jsr305.version>
|
||||
<grpc.version>1.65.1</grpc.version>
|
||||
<guava.version>32.1.3-jre</guava.version>
|
||||
<guava.version>33.3.1-jre</guava.version>
|
||||
<guava.failureaccess.version>1.0.2</guava.failureaccess.version>
|
||||
<hadoop.version>3.3.6</hadoop.version>
|
||||
<hikaricp.version>4.0.3</hikaricp.version>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user