Moving to a recent JDK is a major step. If we do it only half-way to java 7 this won't significantly change jenkins codebase (we already have some code to benefit from JDK7 when available)
Java 8 introduces major coding style changes that could benefit jenkins, so my proposal 2014-09-24 12:58 GMT+02:00 Laurent Malvert <[email protected]>: > +1. > > I think moving to at least Java 7 would be beneficial. However I doubt > there'll be enough pull to move directly to Java 8. I'd totally be in favor > of it though. > > > On Tue, Sep 23, 2014 at 6:33 PM, nicolas de loof <[email protected] > > wrote: > >> Hi folks, >> >> we had discussions here about requiring java 6 for Jenkins. I don't see a >> major benefit for using it, as new API/feature would offer border-line >> changes to jenkins codebase. Same for Java 7 (which is announced EOL anyway) >> >> Makes me wonder if we could start discussion on migrating to Java 8. This >> would allow use of default methods for interface based extension, lambdas, >> and few other significant features for plugin and core developers. This >> won't prevent people to build project on java 1.1 if they wish. >> >> wdyt ? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Laurent Malvert > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
