[jsword-devel] JDK version

[DM Smith]

Sijo,

When Martin gives the go ahead, we can upgrade Lucene. Also appropriately respond to deprecations.

But as Martin pointed out, there’s nothing else we need to do. All of JSword is using a subset of Java 7 and Java 8.

We shouldn’t change an API merely because we can. We should try to maintain backward compatibility for current front-ends. Most of the code is behind the scenes. Not facing the front-end. But where new code is written, it is fair game.

DM

> On Jun 10, 2017, at 6:36 AM, Sijo Cherian <sijo.cherian at gmail.com> wrote:
> 
> How much work is expected in jsword for j7?
> I can help if multiple developer is needed.
> 
> /sijo
> 
> On Jun 9, 2017 6:07 PM, "DM Smith" <dmsmith at crosswire.org <mailto:dmsmith at crosswire.org>> wrote:
> That was a bit short. Our policy has been to support older devices, such as missionaries have for field work. That has meant supporting 10 year old hardware and operating systems. Given those systems the availability of Java was our limiting factor. That initially was limited by MacOS. By the time mobile came around we were at Java 5 and most mobile was requiring a subset of 1.3. Android changed that, but became the limiting factor.
> 
> That was then. I think it is time to revise that policy. Since then Oracle has taken over the development of Java and has done two things that Sun didn’t do. It has frequent releases and second makes older versions harder to get. Today, Java 8 is the only easily available version. It has been over 2 years since the last public update to Java 7.
> 
> Going to 7 as a minimum may prevent some users from getting a JSword app. They can continue to use the currently available apps.
> 
> The more practical question is how to manage a migration in git. Obviously a branch is in order. The question is whether the branch is for maintenance of the current code and trunk is for Java 7? We could go either way. Let us know which you prefer and why.
> 
> In Him,
> 	DM
> 
> 
>> On Jun 7, 2017, at 7:59 PM, DM Smith <dmsmith at crosswire.org <mailto:dmsmith at crosswire.org>> wrote:
>> 
>> Yes. Go for it. 
>> 
>> Cent from my fone so theer mite be tipos. ;)
>> 
>> On Jun 7, 2017, at 4:33 PM, Martin Denham <mjdenham at gmail.com <mailto:mjdenham at gmail.com>> wrote:
>> 
>>> Android will soon support all JDK 7 features, and some JDK 8 features <https://developer.android.com/studio/preview/features/java8-support.html>, so if there was a desire and no other blockers, then it should be possible for JSword to start targeting at least JDK 7. 
>>> 
>>> Martin
>>> _______________________________________________
>>> jsword-devel mailing list
>>> jsword-devel at crosswire.org <mailto:jsword-devel at crosswire.org>
>>> http://www.crosswire.org/mailman/listinfo/jsword-devel <http://www.crosswire.org/mailman/listinfo/jsword-devel>
>> _______________________________________________
>> jsword-devel mailing list
>> jsword-devel at crosswire.org <mailto:jsword-devel at crosswire.org>
>> http://www.crosswire.org/mailman/listinfo/jsword-devel <http://www.crosswire.org/mailman/listinfo/jsword-devel>
> 
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org <mailto:jsword-devel at crosswire.org>
> http://www.crosswire.org/mailman/listinfo/jsword-devel <http://www.crosswire.org/mailman/listinfo/jsword-devel>
> 
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/jsword-devel/attachments/20170610/8591d526/attachment.html>