This is an automated email from the ASF dual-hosted git repository.

lidavidm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow.git


The following commit(s) were added to refs/heads/main by this push:
     new 97e169a115 MINOR: [Java] Upgrade bcpkix-jdkon15 dependency to 
bcpkix-jdkon18 (#41458)
97e169a115 is described below

commit 97e169a115bcf4e18fffd6c788f6fde648969664
Author: Calvin Kirs <[email protected]>
AuthorDate: Tue Apr 30 17:00:02 2024 +0800

    MINOR: [Java] Upgrade bcpkix-jdkon15 dependency to bcpkix-jdkon18 (#41458)
    
    
    
    ### Rationale for this change
    
    Since bcpkix-jdk15on is no longer being maintained and bcpkix-jdkon18 is 
fully compatible with it, we can replace bcpkix-jdk15on with bcpkix-jdkon18. 
This will ensure continued support and security for our applications.
    FYI: https://www.bouncycastle.org/latest_releases.html
    
    ### What changes are included in this PR?
    
    - Upgrade bcpkix-jdkon15 dependency to bcpkix-jdkon18
    ### Are these changes tested?
    
    - yes
    
    We used the JcaPEMWriter class to convert certificates stored within a 
KeyStore object into PEM format and subsequently write them to a designated 
JcaPEMWriter object. Existing test suites provide comprehensive coverage for 
this functionality.
    
    Authored-by: Calvin Kirs <[email protected]>
    Signed-off-by: David Li <[email protected]>
---
 java/flight/flight-sql-jdbc-core/pom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/java/flight/flight-sql-jdbc-core/pom.xml 
b/java/flight/flight-sql-jdbc-core/pom.xml
index 2e0de90fcf..ef3f2469b7 100644
--- a/java/flight/flight-sql-jdbc-core/pom.xml
+++ b/java/flight/flight-sql-jdbc-core/pom.xml
@@ -126,8 +126,8 @@
 
     <dependency>
       <groupId>org.bouncycastle</groupId>
-      <artifactId>bcpkix-jdk15on</artifactId>
-      <version>1.70</version>
+      <artifactId>bcpkix-jdk18on</artifactId>
+      <version>1.78.1</version>
     </dependency>
   </dependencies>
 

Reply via email to