Re: [all] java release cycle predicament

2018-07-11 Thread Stephen Colebourne
At present, everything works in Java 11, and thats not released yet. Here is day job project with similar setup running Java 11 on Travis https://travis-ci.org/OpenGamma/Strata/builds/401792237 Ultimately, all builds are dependent on many other teams, but while Java 9 was bad, 10 and 11 have gener

Re: [all] java release cycle predicament

2018-07-10 Thread Rob Tompkins
> On Jul 10, 2018, at 12:53 PM, Stephen Colebourne wrote: > > Look at Joda-Convert/Joda-Parent for example. A Java 6 project that > builds on Java 8 or later, and has a module-info.java. > > Cobertura just needs replacing with JaCoCo. > > FindBugs replaced by SpotBugs > > Lots of plugin ver

Re: [all] java release cycle predicament

2018-07-10 Thread Stephen Colebourne
Look at Joda-Convert/Joda-Parent for example. A Java 6 project that builds on Java 8 or later, and has a module-info.java. Cobertura just needs replacing with JaCoCo. FindBugs replaced by SpotBugs Lots of plugin versions updated. And lots of profiles, as per Joda-Convert/Joda-Parent Stephen ht

[all] java release cycle predicament

2018-07-10 Thread Rob Tompkins
Hello all, It occurs to me that we are in a bit of a predicament in terms of being able to remain current with java, if the projected 6-month release to EOL cycle for major versions of java indeed continues. For example, as of now java9 is EOL, yet we still don’t have sufficient build tools (ma