Before anybody asks:
We as a community do want to update ctakes to be a 21st century application.
That means the latest cutting edge versions of java, uima, cleartk, log4j, etc.
If you can devote any time towards making this goal a reality, please let us
know!
If you would like to coordinate a hackathon with modernization as a goal,
please take charge of one and gain the credit! At the very least I will show.
:^)
Thanks all,
Sean
From: Finan, Sean
Sent: Wednesday, May 17, 2023 10:47 PM
To: dev@ctakes.apache.org
Subject: cTAKES build change, javac [EXTERNAL] [SUSPICIOUS]
* External Email - Caution *
Hi all,
I am trying to make this understandable for all readers, so the statements that
follow are simplified or abbreviated without tl/dr context.
There have been recent improvements in the Apache build environments that
require java 11.
Those improvements make the java 8 build environments that ctakes has been
using less than favorable, if not completely untenable.
Things had to be fiddled about until ctakes could build in a java 11
environment.
Though ctakes can now be "built with" java 11, ctakes is "built as a" java 8
application.
You still need java 8 to run ctakes. The simple reason for this is that though
the ctakes jars themselves can build on java 11, many dependencies still
require java 8, and we need to stick to that lowest common denominator. For
the time being.
I have local java 11 builds working and regression tests working (java 8 vs.
11), but given the infinite possible ctakes pipelines I cannot cover everything.
The Apache Jenkins 'maven central'ish builds are also working.
Please post on dev@ any NEW problems that you have building ctakes or any
discrepancies that you see running ctakes pipeline v5-SNAPSHOT 5/16/2023 vs.
5/18/2023.
Thanks all,
Sean
Sean Finan
Research Computing Principal Engineer
Computational Health Informatics Program, Natural Language Processing Lab
Boston Children's Hospital
sean.fi...@tch.harvard.edu
