Hi John, Thank you for the information. I didn't realize that hsqldb had changed its format again. I will keep that in mind if and when another dictionary is released.
Sean ________________________________ From: Petersam, John Contractor <john.peter...@ssa.gov.INVALID> Sent: Friday, July 5, 2024 9:21 AM To: dev@ctakes.apache.org <dev@ctakes.apache.org> Subject: RE: [EXTERNAL] Upgrade to JDK 17 Inquiry * External Email - Caution * Hi Sean, I don't believe the migration from 17 to 21 required any changes at all. The big change was getting to 13, and I did that back when 13 came out. The only changes I've made to stay current since then are general library updates. The only one I haven't been able to update is hsqldb because 2.7.3 isn't compatible with the files created with 2.3.4. I'm planning on updating those in the August/September timeframe so I can check that box as well. Thanks, John -----Original Message----- From: Finan, Sean <sean.fi...@childrens.harvard.edu.INVALID> Sent: Wednesday, July 03, 2024 3:57 PM To: dev@ctakes.apache.org Subject: Re: [EXTERNAL] Upgrade to JDK 17 Inquiry Hi John, Would you be able to share some of the changes that you needed to make for 21? Thanks, Sean ________________________________ From: Petersam, John Contractor <john.peter...@ssa.gov.INVALID> Sent: Wednesday, July 3, 2024 3:45 PM To: dev@ctakes.apache.org <dev@ctakes.apache.org> Subject: RE: [EXTERNAL] Upgrade to JDK 17 Inquiry * External Email - Caution * Hi Ryan, I'm on Java 21 and will migrate to 23 when it comes out. I upgraded it years ago, so I don't remember all the specifics of what I changed. It's not that difficult, but does require making some code modifications as well as updating some dependencies so you will definitely need to roll up your sleeves a bit. Thanks, John -----Original Message----- From: Ryan Swenson <rswen...@nsightlabs.com> Sent: Wednesday, July 03, 2024 3:40 PM To: dev@ctakes.apache.org Subject: [EXTERNAL] Upgrade to JDK 17 Inquiry Hello, We have a major application using Apache cTakes for standardizing clinical laboratory results which has been running on Java 8, and we have had to operate with a security exception, and are now where we will need to assess if we can migrate to Java 17 or ultimately migrate entirely to a new paradigm and approach. Has anyone assessed the effort, are there any breaking changes or compatibility issues, or dependency versioning conflicts that need to be addressed to achieve an upgrade to running under Java 17 and soon, 22? We are in favor of upgrading but we can only maintain the security exception for so long, and are now at a point where if it its either too large of an effort, or a ways out from achieving, we will need to migrate soon. Thanks, Ryan
