Hi Eugenia, Yes it is checked in. I believe Sean is about to publish an updated version of what I checked in for 4.0.1, and what I supplied but didn't check in for 4.0.0 The difference is that his update allows old auth info living in xml files to be ignored, while mine requires it to be explicirtely removed or emptied, and then supplying the key (following instructions I attached to Jira item CT-545.
What you do to upgrade all depends on whether you want to start today or soon. Following those instructions should work now and still be valid when Sean checks in the slightly more permissive version. Peter On Mon, Jan 4, 2021 at 3:54 PM Monogyiou, Eugenia < eugenia.monogy...@nttdata.com> wrote: > Hello, > > Happy New Year! Hope everyone is well! > I am just starting to work on this again and trying to catch up on the > latest... I have not migrated yet , I am just about to... > Peter, is your contribution in the trunk yet and should I be using it or > should I just be following your advice in older posts? Are there JIRA posts > I should be looking into as well? > > Thank you in advance, > > > Kind Regards, > > Eugenia Monogyiou | NTT Data UK > Consulting & IT Solutions Ltd. 1 Royal Exchange, London EC3V 3DG > > Mob: +44 (0)7971623683 Email: eugenia.monogy...@nttdata.com > > -----Original Message----- > From: Peter Abramowitsch <pabramowit...@gmail.com> > Sent: 28 December 2020 09:46 > To: dev@ctakes.apache.org > Subject: Sean... & UMLS > > Hi Sean > > Corresponding with Kean on another matter, It surfaced that people don't > know about the UMLS change in the trunk and those instructions I > distributed to the early adopters didn't get circulated (Gandhi - see other > email). > > Is there anything you'd like me to do to facilitate this? Also what about > the 4.0.0 version I supplied. > > Peter > Disclaimer: This email and any attachments are sent in strictest > confidence for the sole use of the addressee and may contain legally > privileged, confidential, and proprietary data. If you are not the intended > recipient, please advise the sender by replying promptly to this email and > then delete and destroy this email and any attachments without any further > use, copying or forwarding. >
