> On Jun 26, 2018, at 3:48 PM, Colm O hEigeartaigh <[email protected]> wrote: > > +1. Would master stay on Java 8 or move up to Java 10?
I believe it would stay compatible with Java 8, but poms could be updated for Java 10 dependency requirements (jaxb-impl dependency added, api jars added, etc…). Possibly add the module info things. I’m also planning (already started working on it) moving from JUnit 4.12 to 5.2. At this point, I’m just switching to the “vintage” engine as it’s doesn’t change much at all. However, we can start thinking about leveraging some of the new things if we want. Dan > > Colm. > > On Tue, Jun 26, 2018 at 12:33 PM, Daniel Kulp <[email protected]> wrote: > >> >> I’m thinking of creating the 3.2 fixes branch and flipping master over to >> 3.3 at some point later this week or early next week. That should allow >> master to target the changes needed for Java 10/11. Let me know if anyone >> has issues with doing so. >> >> >> >> -- >> Daniel Kulp >> [email protected] <mailto:[email protected]> - http://dankulp.com/blog < >> http://dankulp.com/blog> >> Talend Community Coder - http://coders.talend.com < >> http://coders.talend.com/> >> > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com -- Daniel Kulp [email protected] <mailto:[email protected]> - http://dankulp.com/blog <http://dankulp.com/blog> Talend Community Coder - http://coders.talend.com <http://coders.talend.com/>
