I fully agree with Nicolas. And maybe we could use this chance to jump to v2 of Jenkins and even think about changing/removing/refactor some stuff we currently do with ugly workarounds. I'm sure there are a couple of things core developers would love to have fixed... And plugins should?/could? then really express there compatibility with the new version. regards Domi
On 24.09.2014, at 10:17, nicolas de loof <[email protected]> wrote: > Changed the thread topic, as it sounds it's not appealing enough to get > feedback :) > > 2014-09-23 18:33 GMT+02:00 nicolas de loof <[email protected]>: > 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. -- 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.
