Choosing Java 8 or 7 for a new component depends on the APIs you want to use for it more so than what's current. I hear people are still using Java 6, but I doubt those projects are adapting new libraries or upgrading any of their dependencies as it is...
On 27 April 2017 at 09:41, Gilles <gil...@harfang.homelinux.org> wrote: > On Thu, 27 Apr 2017 14:49:01 +0200, Gilles wrote: > >> Hi. >> >> The POM indicates: >> >> <maven.compiler.source>1.6</maven.compiler.source> >> <maven.compiler.target>1.6</maven.compiler.target> >> >> but also: >> >> <commons.release.desc>(requires Java 7+)</commons.release.desc> >> >> Which is wrong? >> >> > Also, please not that keeping 1.6 compatibility seems to complicate > the Jenkins configuration: > https://builds.apache.org/view/Apache%20Commons/job/Commons_ > Numbers/14/console > > For a new component, shouldn't we just go to Java 8? > > > Gilles > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- Matt Sicker <boa...@gmail.com>
