1- From fc26f5691405aac908f4ecfa4682d53b1916bc07 Mon Sep 17 00:00:00 2001
1+ From e50854cc27155f33a73253cf4cee73074071026c Mon Sep 17 00:00:00 2001
22From: Razvan-Daniel Mihai <
[email protected] >
33Date: Tue, 6 May 2025 13:11:25 +0200
44Subject: Update all dependencies which have a new patch update available
55
66---
7- pom.xml | 42 +++++++++++++++++++++---------------------
8- 1 file changed, 21 insertions(+), 21 deletions(-)
7+ pom.xml | 46 +++++++++++++++++++++++-- ---------------------
8+ 1 file changed, 23 insertions(+), 23 deletions(-)
99
1010diff --git a/pom.xml b/pom.xml
11- index e4be54a0ad..6202b48156 100644
11+ index e4be54a0ad..adb7cd401d 100644
1212--- a/pom.xml
1313+++ b/pom.xml
1414@@ -566,7 +566,7 @@
1515 in the dependencyManagement section as it could still lead to different versions of netty
1616 modules and cause trouble if we only rely on transitive dependencies.
1717 -->
1818- <netty4.version>4.1.116.Final</netty4.version>
19- + <netty4.version>4.1.117 .Final</netty4.version>
19+ + <netty4.version>4.1.122 .Final</netty4.version>
2020 <!-- end HBASE-15925 default hadoop compatibility values -->
2121 <audience-annotations.version>0.13.0</audience-annotations.version>
2222 <!--
@@ -48,8 +48,9 @@ index e4be54a0ad..6202b48156 100644
4848 <jaxb-api.version>2.3.1</jaxb-api.version>
4949 <servlet.api.version>3.1.0</servlet.api.version>
5050 <wx.rs.api.version>2.1.1</wx.rs.api.version>
51- <tomcat.jasper.version>9.0.93</tomcat.jasper.version>
51+ - <tomcat.jasper.version>9.0.93</tomcat.jasper.version>
5252- <jruby.version>9.3.13.0</jruby.version>
53+ + <tomcat.jasper.version>9.0.106</tomcat.jasper.version>
5354+ <jruby.version>9.3.15.0</jruby.version>
5455 <junit.version>4.13.2</junit.version>
5556 <hamcrest.version>1.3</hamcrest.version>
@@ -70,8 +71,8 @@ index e4be54a0ad..6202b48156 100644
7071 <!--Make sure these joni/jcodings are compatible with the versions used by jruby-->
7172- <joni.version>2.2.1</joni.version>
7273- <jcodings.version>1.0.58</jcodings.version>
73- + <joni.version>2.2.3 </joni.version>
74- + <jcodings.version>1.0.61 </jcodings.version>
74+ + <joni.version>2.2.6 </joni.version>
75+ + <jcodings.version>1.0.63 </jcodings.version>
7576 <spy.version>2.12.3</spy.version>
7677- <bouncycastle.version>1.78</bouncycastle.version>
7778- <skyscreamer.version>1.5.1</skyscreamer.version>
@@ -80,7 +81,7 @@ index e4be54a0ad..6202b48156 100644
8081 <kerby.version>1.0.1</kerby.version>
8182 <commons-crypto.version>1.1.0</commons-crypto.version>
8283 <curator.version>4.2.0</curator.version>
83- @@ -642,27 +642,27 @@
84+ @@ -642,34 +642,34 @@
8485 <lifecycle.mapping.version>1.0.0</lifecycle.mapping.version>
8586 <maven.antrun.version>1.8</maven.antrun.version>
8687 <maven.bundle.version>3.3.0</maven.bundle.version>
@@ -112,7 +113,15 @@ index e4be54a0ad..6202b48156 100644
112113- <snappy.version>1.1.10.4</snappy.version>
113114- <zstd-jni.version>1.5.5-2</zstd-jni.version>
114115+ <snappy.version>1.1.10.7</snappy.version>
115- + <zstd-jni.version>1.5.6-9 </zstd-jni.version>
116+ + <zstd-jni.version>1.5.7-3 </zstd-jni.version>
116117 <!--
117118 Note that the version of protobuf shipped in hbase-thirdparty must match the version used
118119 in hbase-protocol-shaded and hbase-examples. The version of jackson-[annotations,core,
120+ databind] must be kept in sync with the version of jackson-jaxrs-json-provider shipped in
121+ hbase-thirdparty.
122+ -->
123+ - <hbase-thirdparty.version>4.1.10</hbase-thirdparty.version>
124+ + <hbase-thirdparty.version>4.1.11</hbase-thirdparty.version>
125+ <!-- Coverage properties -->
126+ <jacoco.version>0.8.8</jacoco.version>
127+ <jacocoArgLine/>
0 commit comments