Hi all, I have requested a vote on the release by the Apache cTAKES Project Management Committee (PMC). The vote will end at 5:pm next Monday, September 16.
If you have any issues with the 6.0.0 candidate, please report them by that time. Thank you, Sean ________________________________ From: Finan, Sean Sent: Tuesday, August 27, 2024 6:12 PM To: dev@ctakes.apache.org <dev@ctakes.apache.org>; u...@ctakes.apache.org <u...@ctakes.apache.org> Subject: Please test the cTAKES-6.0.0 candidate for release Hi all, There is a candidate for version 6.0.0 of Apache cTAKES source code in a staging repository: https://repository.apache.org/content/repositories/staging/org/apache/ctakes/ctakes/6.0.0/ The code is contained within the file: https://repository.apache.org/content/repositories/staging/org/apache/ctakes/ctakes/6.0.0/ctakes-6.0.0-source-release.zip You can also get the source code from GitHub: https://github.com/apache/ctakes/releases/tag/ctakes-6.0.0 6.0.0 has the same functionality as the 5.1.0 release. The difference is that, wherever possible, third-party dependencies are upgraded. The primary reason for the upgrade is to minimize vulnerabilities, but it is also nice to be able to take advantage of newer capabilities of those libraries. Among many smaller updates, cTAKES now uses: Java 17 (up from 8) UIMA 3 (up from 2) slf4j* (replaces log4j 1) I welcome you all to test your favorite pipeline(s) and report any issues. Cheers to all who have helped so far with this release! Sean * Some notes on the slf4j upgrade: All of the code contained with cTAKES source itself uses only slf4j. When you compile and run using maven (or an IDE), log4j v2 will be used as the logger implementation. You can disable this behavior by disabling the maven profile named "use-log4j", but you will then need to provide your own logger implementation. See slf4j documentation if you don't know what this means. If you don't know what it means then you are probably fine leaving it as-is. When you build a cTAKES installation (mvn package), log4j v2 will be included in the installation. You can prevent this by disabling the "use-log4j" maven profile. With the default build behavior ("use-log4j" enabled), log4j v2 jars will be placed in a config/ directory, not the lib/ directory. This should make manual deletion easier and safer.
