Hi Andrey It would be good , if you update some steps how to setup new LVG. (Have also cloned your repo.)
On Sun, Jan 29, 2017 at 5:59 PM, Andrey Kurdumov <kant2...@googlemail.com> wrote: > I update code in GitHub to include LVG 2017 > > 2017-01-29 15:29 GMT+06:00 Andrey Kurdumov <kant2...@googlemail.com>: > > > I ask guy who publish LVG to Maven update to version 2017, so I have to > > update my repository with LVG 2017 version. If you interested, I could > > update LVG to that version too. Now that's just simple change in pom.xml > > > > 2017-01-29 14:39 GMT+06:00 Finan, Sean <sean.fi...@childrens.harvard.edu > >: > > > >> Hi Andrey, > >> > >> You have recently been a great contributor to ctakes , and I really > >> appreciate that. You have answered devlist questions and your LVG > update > >> is a seriously big deal. Because of this, you are probably very > interested > >> in the upcoming release. You may have read emails that were on the > devlist > >> these past two days. I would like to assure you that no matter what > could > >> be read into these emails (ok, I can be a little grouchy before the > coffee > >> sets in) there are at least a couple of us who really want to get LVG > >> updated and will try our best to make certain that the next release > >> includes the improvement. We are happy and impressed with your > initiative > >> and furnishing a fully implemented update, and the 3.2.3 branch made a > few > >> weeks ago will just not pass muster in our opinion. Ergh, now I sound > like > >> a politician. That is not intended. I just want you to know that even > >> though recent emails may imply that there is an immature power struggle, > >> that is not the case. I think that everybody in the ctakes community > wants > >> to get a release out asap, and everybody wants it to be a quality > release. > >> Postponing the release a few weeks to get your updates into the codebase > >> is, in my opinion, really important. I just want to let you know that > in > >> case you were aware of the 3.2.3 RC cut made a few weeks ago and worry > that > >> the update will not get into the official cut. I will do what I can to > >> move ctakes into 2017. > >> > >> Regards, > >> Sean > >> > >> -----Original Message----- > >> From: Andrey Kurdumov [mailto:kant2...@googlemail.com] > >> Sent: Thursday, January 19, 2017 6:49 AM > >> To: cTakes developers list > >> Subject: Update LVG to 2016 version > >> > >> As I promise, I udpate cTakes to support LVG version 2016 year. > >> > >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github. > >> com_kant2002_cTakes&d=DwIBaQ&c=qS4goWBT7poplM69zy_3xhKwEW14J > >> ZMSdioCoppxeFU&r=fs67GvlGZstTpyIisCYNYmQCP6r0bcpKGd4f7d4gTao > >> &m=RdfyvGDEhgrlIGv4Ue0X6DViLFyykHEokJgGzgoG5Vs&s=IJWxluJDIVh > >> ugnzWsfRl0TzL0LWzW6_kunc_GRJVew4&e= > >> > >> Please take a look. > >> In the github following modifications to current version of cTakes > >> - Removed two large files to make project fit GitHub restrictions. > >> - Some very small cleanup which placed in separate commit. > >> - Some fixes to ytex related tests, that's was required for me to pass > >> mvn install command. > >> > >> Assumptions: > >> - User should update ctakesnormx and other databases from HSQLdb 1.8 to > >> HSQLDB 2.3.4 > >> > >> I already sign Apache ICLA as user akurdyumov for another project > (Apache > >> Cordova) so if you want update cTakes to LVG2016 please use my code. If > I > >> need something else to submit code to cTakes project, let me know. > >> > > > > > -- with Regards Shahid Ashraf
