Johnsd11 commented on issue #60:
URL: https://github.com/apache/ctakes/issues/60#issuecomment-2835984038

   In short (I have to run right now):
   
   I am really glad that your employer will give you time to work with ctakes!
   
   #1 The jdk 11 build compatibility was a necessity.  It turned out that the 
Apache Jenkins system no longer has a version of maven built with java 8.  They 
seem to also be bumping up their lowest version of java.
   Unless I just couldn't find one.  It is still a selectable choice in the 
Jenkins configuration wizards, it just doesn't actually exist.  According to 
jira reports others found the same thing.
   So, the only solution was for me to make ctakes buildable with jdk 11 and 
maven built with jdk 11.  However, it builds through java 11 as java 8 
compatible byte code.  That was done for our CI on Jenkins.  I can still build 
ctakes with jdk 8.
   
    #2 I am not certain what issues you had.  Unfortunately my employer's email 
system mangles anything that looks like a link, and they become completely 
unreadable.
   
   #3 Dennis Johns and I are trying to get the 5.0 wiki into shape, including 
differences between versions 4 and 5.
   You guessed right about pbj.  It stands for "Python Bridge to Java" and uses 
artemis as a go-between for ctakes and python pipelines.  Though it allows 
python to java, it can be used pretty much any way you would imagine.  java to 
java, python to python, java-python-java, python-java-python, scaling out, 
joining, splitting tasks between different systems, etc.  There are a few 
java-python-java examples in the ctakes resources, one of which uses some 
python from our friends at cnlpt
   (https://github.com/Machine-Learning-for-Medical-Language/cnlp_transformers).
   
   
   Unfortunately dictionary lookup doesn't have any recent major improvements.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to