<div dir="ltr"><div>Hi DM,</div><div><br></div>My comment regarding JDK 7 was just for information. I don't have any need to jump to JDK 7. I just had the feeling the only reason we were still on 6 was because of Android, but it seems like I was wrong.<div><br></div><div>Martin<br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 10 June 2017 at 11:36, Sijo Cherian <span dir="ltr"><<a href="mailto:sijo.cherian@gmail.com" target="_blank">sijo.cherian@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">How much work is expected in jsword for j7?<br>I can help if multiple developer is needed.<span class="HOEnZb"><font color="#888888"><br><div data-smartmail="gmail_signature"><br>/sijo</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Jun 9, 2017 6:07 PM, "DM Smith" <<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">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><div><br></div><div>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><br></div><div>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><br></div><div>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><br></div><div>In Him,</div><div><span class="m_-2990501898536063568m_6078293358732237301Apple-tab-span" style="white-space:pre-wrap"> </span>DM</div><div><div><br></div><div><br><div><blockquote type="cite"><div>On Jun 7, 2017, at 7:59 PM, DM Smith <<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>> wrote:</div><br class="m_-2990501898536063568m_6078293358732237301Apple-interchange-newline"><div><div dir="auto"><div>Yes. Go for it. <br><br>Cent from my fone so theer mite be tipos. ;)</div><div><br>On Jun 7, 2017, at 4:33 PM, Martin Denham <<a href="mailto:mjdenham@gmail.com" target="_blank">mjdenham@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Android will soon support <a href="https://developer.android.com/studio/preview/features/java8-support.html" target="_blank">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><br></div><div>Martin</div></div>
</div></blockquote><blockquote type="cite"><div><span>______________________________<wbr>_________________</span><br><span>jsword-devel mailing list</span><br><span><a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a></span><br><span><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailm<wbr>an/listinfo/jsword-devel</a></span><br></div></blockquote></div>______________________________<wbr>_________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailm<wbr>an/listinfo/jsword-devel</a><br></div></blockquote></div><br></div></div></div></div><br>______________________________<wbr>_________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org" target="_blank">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailm<wbr>an/listinfo/jsword-devel</a><br>
<br></blockquote></div></div>
</div></div><br>______________________________<wbr>_________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/<wbr>mailman/listinfo/jsword-devel</a><br>
<br></blockquote></div><br></div>