While the initial thought of doing it in steps over the next two LTS's sounds nice, after pondering it more I don't think we need the added fragmentation. Changing to 7 or 8 will require me to install a "legacy" Jenkins for me to build on a system that barely has Java 6. I might as well bundle Java7 slaves into that and not end up with three Jenkins installs.
I don't know of any plugins that currently use Scala, but moving to Java8 would help from deterring them since they are moving to Java8. - Thomas From: James Nord <jamestn...@gmail.com<mailto:jamestn...@gmail.com>> Reply-To: "jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>" <jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>> Date: Tuesday, March 24, 2015 at 5:54 AM To: "jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>" <jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>> Subject: Re: Proposal : Jenkins to require Java 8 I think multi-catch and try with resources are big enough on their own to take advantage of in java 7 :-) The syntactic sugar of numerical literals with underscores, and the generic type inference although sugar will make code more readable. As for Java8 bringing usefull things, streams to those that aren't in the know can create very under-performing code when used ([in]correctly) at scale and Lambdas despite Jesse's love of them are a half baked implementation that is oft (ab)used to create unintelligible code and the time API doesn't bring much that we couldn't do if we adopted JodaTime. +1 to get the next LTS as Java7 only and the one after as Java8 only. On Tuesday, 24 March 2015 10:42:02 UTC, nicolas de loof wrote: As said when I opened this topic, I can't see major benefit in requiring Java 7 from a developer point of view (some syntactic sugar, few new API, what else ?), compared to huge benefit of Java 8 to review API design and extensibility. 2015-03-24 11:36 GMT+01:00 Stephen Connolly <stephen.al...@gmail.com<javascript:>>: I think we could start looking at requiring Java 7 as a minimum for Runtime of Jenkins... given that Maven 3.3.1 has moved its minimum runtime to Java 7... if we want to bump the evil plugin version to use the Maven 3.3.1 embedded jars we will have to bump Jenkins to require Java 7 as a minimum... never mind that Java 7 goes EOL next month On 24 March 2015 at 10:33, James Nord <james...@gmail.com<javascript:>> wrote: Rejoice! IBM AIX and z/OS now have a GA Java8 version. http://www-01.ibm.com/support/docview.wss?uid=swg21696670 Is it time to revisit this once more? /James On Thursday, 25 September 2014 16:20:35 UTC+1, Jesse Glick wrote: On Wed, Sep 24, 2014 at 8:47 PM, Mark Waite <mark.ea...@gmail.com> wrote: > I added a new test to the git client plugin which depended on a Java 7 NIO > feature. It failed to compile in my test configuration with Java 6. I think it is fine to require Java 7 in tests; there was already a proposal which met with no controversy to require 7 for building plugins, while continuing to use -target 6 and Animal Sniffer to prevent accidental use of 7+ APIs or bytecode (*). Requiring 8 for building plugins, and thus allowing -source 8 features in src/test/java/**/*.java (**), would be a natural next step, a bit controversial but much less so than requiring 8 for running Jenkins itself. (*) Of course this means functional tests do not find runtime problems occurring on 6 despite lack of linkage errors. But the alternative of running tests on 6 just means the reverse problem, that behavioral changes in 7 which break the plugin are not caught; and this is worse, since many more people will really be running on 7. (**) The upcoming version of Animal Sniffer allows you to skip checks on test-scope dependencies. But it might not yet allow checks to be skipped on src/test/java/**/*.java, which is not a dependency; will need to look into it. -- 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 jenkinsci-de...@googlegroups.com<javascript:>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-dev/c7fd3bd4-26f6-488f-a4bc-52bbf0a8dbad%40googlegroups.com?utm_medium=email&utm_source=footer>. 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 jenkinsci-de...@googlegroups.com<javascript:>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMy1JAFugQHay92Uj1WA%3DZF_uBOQcWQ%3DYWjKa0bJLm9n2w%40mail.gmail.com?utm_medium=email&utm_source=footer>. 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 jenkinsci-dev+unsubscr...@googlegroups.com<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/030973cc-703d-4314-80b9-a83a1693b3f4%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-dev/030973cc-703d-4314-80b9-a83a1693b3f4%40googlegroups.com?utm_medium=email&utm_source=footer>. 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D136CBC2.11412%25thomas.suckow%40pnnl.gov. For more options, visit https://groups.google.com/d/optout.
