You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@opennlp.apache.org by Jörn Kottmann <ko...@gmail.com> on 2013/11/05 09:35:07 UTC
Re: Move to Java 7
We are on Java5 currently, that makes the build for a release more and
more inconvenient because you have to install
a Java5 VM to get it done.
No, other than this there are no strong reasons as far as I am aware of
to move forward to Java 6 or Java 7, both versions don't offer
any new exciting features which improve the user experience of OpenNLP.
Though it is nice to use the new API in Java 6/7 here and there.
OpenNLP 1.6.0 will break backward compatibility in some ways, e.g.
through the refactoring of the machine learning code, but
this will only affect users who sub-classed a component or copied over code.
Should we reconsider the update, and wait a bit longer? Would it make
sense to move forward to Java 6?
Jörn
On 10/31/2013 02:07 AM, Lance Norskog wrote:
> My ability to search email has just now died, so I can't find the
> recent discussion. Is there a compelling reason not to use 5 or 6? Any
> deal-breakers? Open source projects have a range of ways to trip up
> and alienate users, and breaking compatibility is in the top list.
> Hadoop & Ruby have lost traction by changing APIs. Python 3 is not
> backward-compatible as in 'you have to recode these few little things
> we don't like any more' and I only see 2.7 apps when I download them.
>
> I don't know if Lucene is on Java 7 yet. They have been very
> conservative about these upgrades in the past, because they have a
> really large installed base. Lucene/Solr is one of the top 5 Apache
> downloads. As to my little project, nobody uses it.
>
> Lance
>
> On 10/30/2013 12:39 AM, Jörn Kottmann wrote:
>> I know you are working on an OpenNLP contrib to Lucene,
>> would this be affected through the update?
>>
>> Jörn
>>
>> On 10/30/2013 08:36 AM, Jörn Kottmann wrote:
>>> Hi Lance,
>>>
>>> please share you concerns with us. OpenNLP 1.6.0 will
>>> require a Java 7 VM, if other parts of your project only require
>>> Java 6 this will all work together on a Java 7 VM.
>>>
>>> Do you have a production system where you can only run java 6 VMs?
>>>
>>> At which time do you plan to update to java 7? It will probably take
>>> us a few
>>> month until OpenNLP 1.6.0 is out.
>>>
>>> Jörn
>>>
>>> On 10/29/2013 11:02 PM, Lance Norskog wrote:
>>>> Will this screw up a project that uses OpenNLP jar if the project
>>>> is still on Java 6?
>>>>
>>>> Lance
>>>>
>>>> On 10/29/2013 03:29 AM, Mark G wrote:
>>>>> Ok, thanks! I didn't know which server was the build server...
>>>>> same as SVN?
>>>>> I will try to commit some java 7 code now
>>>>> MG
>>>>>
>>>>>
>>>>> On Tue, Oct 29, 2013 at 6:25 AM, Jörn Kottmann
>>>>> <ko...@gmail.com> wrote:
>>>>>
>>>>>> On 10/29/2013 11:11 AM, Mark G wrote:
>>>>>>
>>>>>>> OK, I committed the POM only just to see if the CI server has
>>>>>>> Java 7 in
>>>>>>> it's path. Since we haven't gotten a build error yet, it may be
>>>>>>> fine.
>>>>>>> Haven't tried committing any code with J7 objects.
>>>>>>>
>>>>>> I updated the configuration on the build server is now to Java 7,
>>>>>> to do
>>>>>> this you have to log
>>>>>> in there with your apache id and then go to "Configuration" of
>>>>>> the OpenNLP
>>>>>> project.
>>>>>>
>>>>>> Jörn
>>>>>>
>>>>
>>>
>>
>
Re: Move to Java 7
Posted by Jörn Kottmann <ko...@gmail.com>.
Is anbody running OpenNLP on Android? As far was I know the Android
SDK is only Java 6.
Jörn
On 11/05/2013 09:43 AM, Samik Raychaudhuri wrote:
> Another vote of support for Java 7. It makes sense to move to the most
> recent version.
>
> On 05/11/2013 2:13 PM, amcmurry wrote:
>> Isn't JDK6 already end of life?
>> Java 7 is stable, Java 8 is upcoming.
>>
>> Java 5 is very old.
>>
>> FWIW
>>
>> On Nov 5, 2013, at 12:35 AM, Jörn Kottmann <ko...@gmail.com> wrote:
>>
>>> We are on Java5 currently, that makes the build for a release more
>>> and more inconvenient because you have to install
>>> a Java5 VM to get it done.
>>>
>>> No, other than this there are no strong reasons as far as I am aware
>>> of to move forward to Java 6 or Java 7, both versions don't offer
>>> any new exciting features which improve the user experience of
>>> OpenNLP. Though it is nice to use the new API in Java 6/7 here and
>>> there.
>>>
>>> OpenNLP 1.6.0 will break backward compatibility in some ways, e.g.
>>> through the refactoring of the machine learning code, but
>>> this will only affect users who sub-classed a component or copied
>>> over code.
>>>
>>> Should we reconsider the update, and wait a bit longer? Would it
>>> make sense to move forward to Java 6?
>>>
>>> Jörn
>>>
>>> On 10/31/2013 02:07 AM, Lance Norskog wrote:
>>>> My ability to search email has just now died, so I can't find the
>>>> recent discussion. Is there a compelling reason not to use 5 or 6?
>>>> Any deal-breakers? Open source projects have a range of ways to
>>>> trip up and alienate users, and breaking compatibility is in the
>>>> top list. Hadoop & Ruby have lost traction by changing APIs. Python
>>>> 3 is not backward-compatible as in 'you have to recode these few
>>>> little things we don't like any more' and I only see 2.7 apps when
>>>> I download them.
>>>>
>>>> I don't know if Lucene is on Java 7 yet. They have been very
>>>> conservative about these upgrades in the past, because they have a
>>>> really large installed base. Lucene/Solr is one of the top 5 Apache
>>>> downloads. As to my little project, nobody uses it.
>>>>
>>>> Lance
>>>>
>>>> On 10/30/2013 12:39 AM, Jörn Kottmann wrote:
>>>>> I know you are working on an OpenNLP contrib to Lucene,
>>>>> would this be affected through the update?
>>>>>
>>>>> Jörn
>>>>>
>>>>> On 10/30/2013 08:36 AM, Jörn Kottmann wrote:
>>>>>> Hi Lance,
>>>>>>
>>>>>> please share you concerns with us. OpenNLP 1.6.0 will
>>>>>> require a Java 7 VM, if other parts of your project only require
>>>>>> Java 6 this will all work together on a Java 7 VM.
>>>>>>
>>>>>> Do you have a production system where you can only run java 6 VMs?
>>>>>>
>>>>>> At which time do you plan to update to java 7? It will probably
>>>>>> take us a few
>>>>>> month until OpenNLP 1.6.0 is out.
>>>>>>
>>>>>> Jörn
>>>>>>
>>>>>> On 10/29/2013 11:02 PM, Lance Norskog wrote:
>>>>>>> Will this screw up a project that uses OpenNLP jar if the
>>>>>>> project is still on Java 6?
>>>>>>>
>>>>>>> Lance
>>>>>>>
>>>>>>> On 10/29/2013 03:29 AM, Mark G wrote:
>>>>>>>> Ok, thanks! I didn't know which server was the build server...
>>>>>>>> same as SVN?
>>>>>>>> I will try to commit some java 7 code now
>>>>>>>> MG
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Oct 29, 2013 at 6:25 AM, Jörn Kottmann
>>>>>>>> <ko...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> On 10/29/2013 11:11 AM, Mark G wrote:
>>>>>>>>>
>>>>>>>>>> OK, I committed the POM only just to see if the CI server has
>>>>>>>>>> Java 7 in
>>>>>>>>>> it's path. Since we haven't gotten a build error yet, it may
>>>>>>>>>> be fine.
>>>>>>>>>> Haven't tried committing any code with J7 objects.
>>>>>>>>>>
>>>>>>>>> I updated the configuration on the build server is now to Java
>>>>>>>>> 7, to do
>>>>>>>>> this you have to log
>>>>>>>>> in there with your apache id and then go to "Configuration" of
>>>>>>>>> the OpenNLP
>>>>>>>>> project.
>>>>>>>>>
>>>>>>>>> Jörn
>>>>>>>>>
>>
>
>
Re: Move to Java 7
Posted by amcmurry <mc...@gmail.com>.
FYI: Official dates for End Of Life for *Public Updates*
http://www.oracle.com/technetwork/java/eol-135779.html
Java 5 EOL Oct 2009
Java 6 EOL Feb 2013
Java 7 EOL Mar 2015
On Nov 5, 2013, at 12:51 AM, Jörn Kottmann <ko...@gmail.com> wrote:
> On 11/05/2013 09:49 AM, ARUN Thundyill Saseendran wrote:
>> *I vote for Java 7*
>>
>> I believe it is high time we move on to Java 7.
>> We should have ported a long time back so that we wouldn't have had these
>> problems now.
>
> There are no problems. OpenNLP 1.5.3 is Java 5 and runs well on all three versions,
> 5, 6 and 7.
>
> Jörn
Re: Move to Java 7
Posted by Jörn Kottmann <ko...@gmail.com>.
On 11/05/2013 09:49 AM, ARUN Thundyill Saseendran wrote:
> *I vote for Java 7*
>
> I believe it is high time we move on to Java 7.
> We should have ported a long time back so that we wouldn't have had these
> problems now.
There are no problems. OpenNLP 1.5.3 is Java 5 and runs well on all
three versions,
5, 6 and 7.
Jörn
Re: Move to Java 7
Posted by ARUN Thundyill Saseendran <at...@gmail.com>.
*I vote for Java 7*
I believe it is high time we move on to Java 7.
We should have ported a long time back so that we wouldn't have had these
problems now.
Thanks
Arun
On Tue, Nov 5, 2013 at 2:13 PM, Samik Raychaudhuri <sa...@gmail.com> wrote:
> Another vote of support for Java 7. It makes sense to move to the most
> recent version.
>
> On 05/11/2013 2:13 PM, amcmurry wrote:
>
>> Isn't JDK6 already end of life?
>> Java 7 is stable, Java 8 is upcoming.
>>
>> Java 5 is very old.
>>
>> FWIW
>>
>> On Nov 5, 2013, at 12:35 AM, Jörn Kottmann <ko...@gmail.com> wrote:
>>
>> We are on Java5 currently, that makes the build for a release more and
>>> more inconvenient because you have to install
>>> a Java5 VM to get it done.
>>>
>>> No, other than this there are no strong reasons as far as I am aware of
>>> to move forward to Java 6 or Java 7, both versions don't offer
>>> any new exciting features which improve the user experience of OpenNLP.
>>> Though it is nice to use the new API in Java 6/7 here and there.
>>>
>>> OpenNLP 1.6.0 will break backward compatibility in some ways, e.g.
>>> through the refactoring of the machine learning code, but
>>> this will only affect users who sub-classed a component or copied over
>>> code.
>>>
>>> Should we reconsider the update, and wait a bit longer? Would it make
>>> sense to move forward to Java 6?
>>>
>>> Jörn
>>>
>>> On 10/31/2013 02:07 AM, Lance Norskog wrote:
>>>
>>>> My ability to search email has just now died, so I can't find the
>>>> recent discussion. Is there a compelling reason not to use 5 or 6? Any
>>>> deal-breakers? Open source projects have a range of ways to trip up and
>>>> alienate users, and breaking compatibility is in the top list. Hadoop &
>>>> Ruby have lost traction by changing APIs. Python 3 is not
>>>> backward-compatible as in 'you have to recode these few little things we
>>>> don't like any more' and I only see 2.7 apps when I download them.
>>>>
>>>> I don't know if Lucene is on Java 7 yet. They have been very
>>>> conservative about these upgrades in the past, because they have a really
>>>> large installed base. Lucene/Solr is one of the top 5 Apache downloads. As
>>>> to my little project, nobody uses it.
>>>>
>>>> Lance
>>>>
>>>> On 10/30/2013 12:39 AM, Jörn Kottmann wrote:
>>>>
>>>>> I know you are working on an OpenNLP contrib to Lucene,
>>>>> would this be affected through the update?
>>>>>
>>>>> Jörn
>>>>>
>>>>> On 10/30/2013 08:36 AM, Jörn Kottmann wrote:
>>>>>
>>>>>> Hi Lance,
>>>>>>
>>>>>> please share you concerns with us. OpenNLP 1.6.0 will
>>>>>> require a Java 7 VM, if other parts of your project only require
>>>>>> Java 6 this will all work together on a Java 7 VM.
>>>>>>
>>>>>> Do you have a production system where you can only run java 6 VMs?
>>>>>>
>>>>>> At which time do you plan to update to java 7? It will probably take
>>>>>> us a few
>>>>>> month until OpenNLP 1.6.0 is out.
>>>>>>
>>>>>> Jörn
>>>>>>
>>>>>> On 10/29/2013 11:02 PM, Lance Norskog wrote:
>>>>>>
>>>>>>> Will this screw up a project that uses OpenNLP jar if the project is
>>>>>>> still on Java 6?
>>>>>>>
>>>>>>> Lance
>>>>>>>
>>>>>>> On 10/29/2013 03:29 AM, Mark G wrote:
>>>>>>>
>>>>>>>> Ok, thanks! I didn't know which server was the build server... same
>>>>>>>> as SVN?
>>>>>>>> I will try to commit some java 7 code now
>>>>>>>> MG
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Oct 29, 2013 at 6:25 AM, Jörn Kottmann <ko...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> On 10/29/2013 11:11 AM, Mark G wrote:
>>>>>>>>>
>>>>>>>>> OK, I committed the POM only just to see if the CI server has
>>>>>>>>>> Java 7 in
>>>>>>>>>> it's path. Since we haven't gotten a build error yet, it may be
>>>>>>>>>> fine.
>>>>>>>>>> Haven't tried committing any code with J7 objects.
>>>>>>>>>>
>>>>>>>>>> I updated the configuration on the build server is now to Java
>>>>>>>>> 7, to do
>>>>>>>>> this you have to log
>>>>>>>>> in there with your apache id and then go to "Configuration" of the
>>>>>>>>> OpenNLP
>>>>>>>>> project.
>>>>>>>>>
>>>>>>>>> Jörn
>>>>>>>>>
>>>>>>>>>
>>
>
--
Re: Move to Java 7
Posted by Samik Raychaudhuri <sa...@gmail.com>.
Another vote of support for Java 7. It makes sense to move to the most
recent version.
On 05/11/2013 2:13 PM, amcmurry wrote:
> Isn't JDK6 already end of life?
> Java 7 is stable, Java 8 is upcoming.
>
> Java 5 is very old.
>
> FWIW
>
> On Nov 5, 2013, at 12:35 AM, Jörn Kottmann <ko...@gmail.com> wrote:
>
>> We are on Java5 currently, that makes the build for a release more and more inconvenient because you have to install
>> a Java5 VM to get it done.
>>
>> No, other than this there are no strong reasons as far as I am aware of to move forward to Java 6 or Java 7, both versions don't offer
>> any new exciting features which improve the user experience of OpenNLP. Though it is nice to use the new API in Java 6/7 here and there.
>>
>> OpenNLP 1.6.0 will break backward compatibility in some ways, e.g. through the refactoring of the machine learning code, but
>> this will only affect users who sub-classed a component or copied over code.
>>
>> Should we reconsider the update, and wait a bit longer? Would it make sense to move forward to Java 6?
>>
>> Jörn
>>
>> On 10/31/2013 02:07 AM, Lance Norskog wrote:
>>> My ability to search email has just now died, so I can't find the recent discussion. Is there a compelling reason not to use 5 or 6? Any deal-breakers? Open source projects have a range of ways to trip up and alienate users, and breaking compatibility is in the top list. Hadoop & Ruby have lost traction by changing APIs. Python 3 is not backward-compatible as in 'you have to recode these few little things we don't like any more' and I only see 2.7 apps when I download them.
>>>
>>> I don't know if Lucene is on Java 7 yet. They have been very conservative about these upgrades in the past, because they have a really large installed base. Lucene/Solr is one of the top 5 Apache downloads. As to my little project, nobody uses it.
>>>
>>> Lance
>>>
>>> On 10/30/2013 12:39 AM, Jörn Kottmann wrote:
>>>> I know you are working on an OpenNLP contrib to Lucene,
>>>> would this be affected through the update?
>>>>
>>>> Jörn
>>>>
>>>> On 10/30/2013 08:36 AM, Jörn Kottmann wrote:
>>>>> Hi Lance,
>>>>>
>>>>> please share you concerns with us. OpenNLP 1.6.0 will
>>>>> require a Java 7 VM, if other parts of your project only require
>>>>> Java 6 this will all work together on a Java 7 VM.
>>>>>
>>>>> Do you have a production system where you can only run java 6 VMs?
>>>>>
>>>>> At which time do you plan to update to java 7? It will probably take us a few
>>>>> month until OpenNLP 1.6.0 is out.
>>>>>
>>>>> Jörn
>>>>>
>>>>> On 10/29/2013 11:02 PM, Lance Norskog wrote:
>>>>>> Will this screw up a project that uses OpenNLP jar if the project is still on Java 6?
>>>>>>
>>>>>> Lance
>>>>>>
>>>>>> On 10/29/2013 03:29 AM, Mark G wrote:
>>>>>>> Ok, thanks! I didn't know which server was the build server... same as SVN?
>>>>>>> I will try to commit some java 7 code now
>>>>>>> MG
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Oct 29, 2013 at 6:25 AM, Jörn Kottmann <ko...@gmail.com> wrote:
>>>>>>>
>>>>>>>> On 10/29/2013 11:11 AM, Mark G wrote:
>>>>>>>>
>>>>>>>>> OK, I committed the POM only just to see if the CI server has Java 7 in
>>>>>>>>> it's path. Since we haven't gotten a build error yet, it may be fine.
>>>>>>>>> Haven't tried committing any code with J7 objects.
>>>>>>>>>
>>>>>>>> I updated the configuration on the build server is now to Java 7, to do
>>>>>>>> this you have to log
>>>>>>>> in there with your apache id and then go to "Configuration" of the OpenNLP
>>>>>>>> project.
>>>>>>>>
>>>>>>>> Jörn
>>>>>>>>
>
Re: Move to Java 7
Posted by amcmurry <mc...@gmail.com>.
Isn't JDK6 already end of life?
Java 7 is stable, Java 8 is upcoming.
Java 5 is very old.
FWIW
On Nov 5, 2013, at 12:35 AM, Jörn Kottmann <ko...@gmail.com> wrote:
> We are on Java5 currently, that makes the build for a release more and more inconvenient because you have to install
> a Java5 VM to get it done.
>
> No, other than this there are no strong reasons as far as I am aware of to move forward to Java 6 or Java 7, both versions don't offer
> any new exciting features which improve the user experience of OpenNLP. Though it is nice to use the new API in Java 6/7 here and there.
>
> OpenNLP 1.6.0 will break backward compatibility in some ways, e.g. through the refactoring of the machine learning code, but
> this will only affect users who sub-classed a component or copied over code.
>
> Should we reconsider the update, and wait a bit longer? Would it make sense to move forward to Java 6?
>
> Jörn
>
> On 10/31/2013 02:07 AM, Lance Norskog wrote:
>> My ability to search email has just now died, so I can't find the recent discussion. Is there a compelling reason not to use 5 or 6? Any deal-breakers? Open source projects have a range of ways to trip up and alienate users, and breaking compatibility is in the top list. Hadoop & Ruby have lost traction by changing APIs. Python 3 is not backward-compatible as in 'you have to recode these few little things we don't like any more' and I only see 2.7 apps when I download them.
>>
>> I don't know if Lucene is on Java 7 yet. They have been very conservative about these upgrades in the past, because they have a really large installed base. Lucene/Solr is one of the top 5 Apache downloads. As to my little project, nobody uses it.
>>
>> Lance
>>
>> On 10/30/2013 12:39 AM, Jörn Kottmann wrote:
>>> I know you are working on an OpenNLP contrib to Lucene,
>>> would this be affected through the update?
>>>
>>> Jörn
>>>
>>> On 10/30/2013 08:36 AM, Jörn Kottmann wrote:
>>>> Hi Lance,
>>>>
>>>> please share you concerns with us. OpenNLP 1.6.0 will
>>>> require a Java 7 VM, if other parts of your project only require
>>>> Java 6 this will all work together on a Java 7 VM.
>>>>
>>>> Do you have a production system where you can only run java 6 VMs?
>>>>
>>>> At which time do you plan to update to java 7? It will probably take us a few
>>>> month until OpenNLP 1.6.0 is out.
>>>>
>>>> Jörn
>>>>
>>>> On 10/29/2013 11:02 PM, Lance Norskog wrote:
>>>>> Will this screw up a project that uses OpenNLP jar if the project is still on Java 6?
>>>>>
>>>>> Lance
>>>>>
>>>>> On 10/29/2013 03:29 AM, Mark G wrote:
>>>>>> Ok, thanks! I didn't know which server was the build server... same as SVN?
>>>>>> I will try to commit some java 7 code now
>>>>>> MG
>>>>>>
>>>>>>
>>>>>> On Tue, Oct 29, 2013 at 6:25 AM, Jörn Kottmann <ko...@gmail.com> wrote:
>>>>>>
>>>>>>> On 10/29/2013 11:11 AM, Mark G wrote:
>>>>>>>
>>>>>>>> OK, I committed the POM only just to see if the CI server has Java 7 in
>>>>>>>> it's path. Since we haven't gotten a build error yet, it may be fine.
>>>>>>>> Haven't tried committing any code with J7 objects.
>>>>>>>>
>>>>>>> I updated the configuration on the build server is now to Java 7, to do
>>>>>>> this you have to log
>>>>>>> in there with your apache id and then go to "Configuration" of the OpenNLP
>>>>>>> project.
>>>>>>>
>>>>>>> Jörn
>>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: Move to Java 7
Posted by Jörn Kottmann <ko...@gmail.com>.
On 11/05/2013 10:18 AM, Richard Eckart de Castilho wrote:
> It is not necessary to have a Java5 VM to do a release for Java 5. Just set the source and target versions in the
> compile plugin and you are fine. I don't have a Java 5 VM since quite some time, but still do releases (e.g. uimaFIT)
> targeting Java 5.
>
> However, there is a risk that non-Java 5 API is being used without being noticed (e.g. new IOException(Throwable)).
> This can be caught by setting up a corresponding Jenkins job or eventually by users after a release, which then may
> require a bug-fix release.
Thanks for this input, we should adjust our release guidelines, even if
we now move to Java7 a new version will be out
one day.
We already have a Jenkins job, and that one will always run with the
corresponding Java version.
Jörn
Re: Move to Java 7
Posted by Mark G <gi...@gmail.com>.
My vote is move to 7. Java 7 has been out for over 2 years.
On Tue, Nov 5, 2013 at 4:18 AM, Richard Eckart de Castilho <
richard.eckart@gmail.com> wrote:
> On 05.11.2013, at 09:35, Jörn Kottmann <ko...@gmail.com> wrote:
>
> > We are on Java5 currently, that makes the build for a release more and
> more inconvenient because you have to install
> > a Java5 VM to get it done.
>
> It is not necessary to have a Java5 VM to do a release for Java 5. Just
> set the source and target versions in the
> compile plugin and you are fine. I don't have a Java 5 VM since quite some
> time, but still do releases (e.g. uimaFIT)
> targeting Java 5.
>
> However, there is a risk that non-Java 5 API is being used without being
> noticed (e.g. new IOException(Throwable)).
> This can be caught by setting up a corresponding Jenkins job or eventually
> by users after a release, which then may
> require a bug-fix release.
>
> -- Richard
Re: Move to Java 7
Posted by Richard Eckart de Castilho <ri...@gmail.com>.
On 05.11.2013, at 09:35, Jörn Kottmann <ko...@gmail.com> wrote:
> We are on Java5 currently, that makes the build for a release more and more inconvenient because you have to install
> a Java5 VM to get it done.
It is not necessary to have a Java5 VM to do a release for Java 5. Just set the source and target versions in the
compile plugin and you are fine. I don't have a Java 5 VM since quite some time, but still do releases (e.g. uimaFIT)
targeting Java 5.
However, there is a risk that non-Java 5 API is being used without being noticed (e.g. new IOException(Throwable)).
This can be caught by setting up a corresponding Jenkins job or eventually by users after a release, which then may
require a bug-fix release.
-- Richard