Re: GIS API
Looks like there are a couple of classes depending on it which can be all removed. Lets clean that up for 1.6.0. Jörn On Thu, May 28, 2015 at 3:51 PM, Joern Kottmann wrote: > Yes, or we can also remove it directly. The package name changed anyway, > we will not be able to support existing code using EventStream with 1.6.0 > without breaking it. > > Please open a jia for it. > > Jörn > > On Thu, May 28, 2015 at 3:49 PM, Russ, Daniel (NIH/CIT) [E] < > dr...@mail.nih.gov> wrote: > >> Sorry, I just saw the interfaces are very different, so there is not easy >> fix. EventStream still should be deprecated. >> Dan >> >> >> On May 28, 2015, at 9:34 AM, Russ, Daniel (NIH/CIT) [E] wrote: >> >> > Hi, >> > >> > The interface for opennlp.tools.maxent.GIS is changing between 1.5 >> and 1.6. This will cause me to have to make many changes in my code that >> could be easily avoided if we change make opennlp.tools.ml.model extend >> ObjectStream. Also, Since EventStream is not used by GIS, is there >> any reason why it is not deprecated? I will put this in JIRA. >> > >> > Thank you >> > Dan >> >> >
Re: GIS API
Yes, or we can also remove it directly. The package name changed anyway, we will not be able to support existing code using EventStream with 1.6.0 without breaking it. Please open a jia for it. Jörn On Thu, May 28, 2015 at 3:49 PM, Russ, Daniel (NIH/CIT) [E] < dr...@mail.nih.gov> wrote: > Sorry, I just saw the interfaces are very different, so there is not easy > fix. EventStream still should be deprecated. > Dan > > > On May 28, 2015, at 9:34 AM, Russ, Daniel (NIH/CIT) [E] wrote: > > > Hi, > > > > The interface for opennlp.tools.maxent.GIS is changing between 1.5 and > 1.6. This will cause me to have to make many changes in my code that could > be easily avoided if we change make opennlp.tools.ml.model extend > ObjectStream. Also, Since EventStream is not used by GIS, is there > any reason why it is not deprecated? I will put this in JIRA. > > > > Thank you > > Dan > >
Re: GIS API
Sorry, I just saw the interfaces are very different, so there is not easy fix. EventStream still should be deprecated. Dan On May 28, 2015, at 9:34 AM, Russ, Daniel (NIH/CIT) [E] wrote: > Hi, > > The interface for opennlp.tools.maxent.GIS is changing between 1.5 and 1.6. > This will cause me to have to make many changes in my code that could be > easily avoided if we change make opennlp.tools.ml.model extend > ObjectStream. Also, Since EventStream is not used by GIS, is there > any reason why it is not deprecated? I will put this in JIRA. > > Thank you > Dan
GIS API
Hi, The interface for opennlp.tools.maxent.GIS is changing between 1.5 and 1.6. This will cause me to have to make many changes in my code that could be easily avoided if we change make opennlp.tools.ml.model extend ObjectStream. Also, Since EventStream is not used by GIS, is there any reason why it is not deprecated? I will put this in JIRA. Thank you Dan
Re: OpenNLP 1.6.0 RC 4 ready for testing
Yes, the sentence detector does not match, but it is such a small change that I would not even investigate. It is an empty line that used to be included in the 1.5.3 output, but it is not included in 1.6.0 anymore: *Output in 1.5.3:* [image: Imagem inline 1] *Output in 1.6.0:* [image: Imagem inline 3] I would ignore the change. Thank you, William 2015-05-28 7:28 GMT-03:00 Joern Kottmann : > The chunker and parser tests are fine now. > > Do you know what's the deal with the sentence detector? > > The compatibility test is marked as failed. Can we leave it like that or > do we have to fix some bugs? > > Jörn > On May 23, 2015 5:35 AM, "William Colen" wrote: > >> Our fourth release candidate is ready for testing. RC 3 failed in the >> compatibility, regression and performance tests, which are fixed in RC 4. >> >> The RC 4 can be downloaded from here: >> http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/ >> >> To use it in a maven build set the version for opennlp-tools or >> opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: >> https://repository.apache.org/content/repositories/orgapacheopennlp-1003 >> >> The current test plan can be found here: >> https://cwiki.apache.org/confluence/display/OPENNLP/TestPlan1.6.0 >> >> Please sign up for tasks in the test plan. >> >> The release plan can be found here: >> >> https://cwiki.apache.org/confluence/display/OPENNLP/ReleasePlanAndTasks1.6.0 >> >> The release contains quite some changes, please refer to the contained >> issue list for details. >> >> For your convenience, a copy of the issue list, as well as the release >> notes and the readme, can be found in the following link: >> >> >> http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/RELEASE_NOTES.html >> >> >> Thank you, >> William >> >
Re: OpenNLP 1.6.0 RC 4 ready for testing
The chunker and parser tests are fine now. Do you know what's the deal with the sentence detector? The compatibility test is marked as failed. Can we leave it like that or do we have to fix some bugs? Jörn On May 23, 2015 5:35 AM, "William Colen" wrote: > Our fourth release candidate is ready for testing. RC 3 failed in the > compatibility, regression and performance tests, which are fixed in RC 4. > > The RC 4 can be downloaded from here: > http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/ > > To use it in a maven build set the version for opennlp-tools or > opennlp-uima to 1.6.0 and add the following URL to your settings.xml file: > https://repository.apache.org/content/repositories/orgapacheopennlp-1003 > > The current test plan can be found here: > https://cwiki.apache.org/confluence/display/OPENNLP/TestPlan1.6.0 > > Please sign up for tasks in the test plan. > > The release plan can be found here: > > https://cwiki.apache.org/confluence/display/OPENNLP/ReleasePlanAndTasks1.6.0 > > The release contains quite some changes, please refer to the contained > issue list for details. > > For your convenience, a copy of the issue list, as well as the release > notes and the readme, can be found in the following link: > > > http://people.apache.org/~colen/releases/opennlp-1.6.0/rc4/RELEASE_NOTES.html > > > Thank you, > William >
