<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">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.<div class=""><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">Going to 7 as a minimum may prevent some users from getting a JSword app. They can continue to use the currently available apps.</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">In Him,</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div class=""><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 7, 2017, at 7:59 PM, DM Smith <<a href="mailto:dmsmith@crosswire.org" class="">dmsmith@crosswire.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">Yes. Go for it. <br class=""><br class="">Cent from my fone so theer mite be tipos. ;)</div><div class=""><br class="">On Jun 7, 2017, at 4:33 PM, Martin Denham <<a href="mailto:mjdenham@gmail.com" class="">mjdenham@gmail.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">Android will soon support <a href="https://developer.android.com/studio/preview/features/java8-support.html" class="">all JDK 7 features, and some JDK 8 features</a>, so if there was a desire and no other blockers, then it should be possible for JSword to start targeting at least JDK 7. <div class=""><br class=""></div><div class="">Martin</div></div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">jsword-devel mailing list</span><br class=""><span class=""><a href="mailto:jsword-devel@crosswire.org" class="">jsword-devel@crosswire.org</a></span><br class=""><span class=""><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" class="">http://www.crosswire.org/mailman/listinfo/jsword-devel</a></span><br class=""></div></blockquote></div>_______________________________________________<br class="">jsword-devel mailing list<br class=""><a href="mailto:jsword-devel@crosswire.org" class="">jsword-devel@crosswire.org</a><br class="">http://www.crosswire.org/mailman/listinfo/jsword-devel<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>