One of our slave machines is a PowerMac G5 computer, running Mac OS X 10.5.8 which is indeed stuck at Java 1.5. We need that slave to test our software on a BigEndian platform. It would be a real pity if we would lose that testing platform!
Jürgen Am Donnerstag, 6. September 2012 09:12:30 UTC+2 schrieb Stephen Connolly: > > On 5 September 2012 23:16, Kohsuke Kawaguchi > <[email protected]<javascript:> > > wrote: > >> On 09/05/2012 01:18 PM, Brian Smith wrote: >> >>> Hi >>> >>> I don't think EOL alone is a good reason to upgrade the runtime >>> dependency, anybody concerned about it can run on a newer JVM anyway. >>> >>> It might help if someone were to outline the benefit of upgrading the >>> language version. >>> >> >> The benefits to developers are: >> >> - We get to use a few APIs that we currently can't rely on. >> (Note that we already do use a number of Java6 APIs in ways that >> gracefully degrades when running on Java5, but this is separate.) >> >> - Some IDE integrations (apparently) work better when what we tell >> as the compiler language level (1.5) matches with the runtime >> requirement (1.6) >> >> - Some language level stuff (like @Override on interface methods) >> causes IDE and javac to disagree, which gets fixed with 1.6. >> >> The benefits are admittedly marginal, but the argument is that the cost >> is marginal, too --- just 2% of users on Java5, and I suspect those people >> aren't updating frequently. >> >> And at some point we need to move on, so I suppose it could well be now. >> >> >> I guess what I'm particularly keen on is if there are any minority >> platforms where Java6 isn't available easily, and/or desperate cries from >> users begging us not to require Java6, if any. >> > > This is really where the issue is. > > If you have Jenkins slaves that are on older OSes which are stuck with > Java 1.5 as the "best" JVM they can run, please shout out now. > > -Stephen > > >> (Personally, I'm neutral on this.) >> >> What's the upside for jenkins dev? Is there something in java 6 people >>> are hankering to use? >>> >>> Personally the only things in java 6 I've found useful were the new >>> concurrent collections and the ResourceBundle hooks. >>> >>> Cheers >>> >>> Brian >>> >>> On 5 September 2012 20:18, domi <[email protected] <javascript:> >>> <mailto:[email protected] <javascript:>>> wrote: >>> >>> Hi all, >>> >>> just after todays meeting on the IRC chat, we startet a discussion >>> about upgrading Jenkins to Java 6. >>> As Java 5 has reached EOL since quite a while, some core developers >>> have asked whether it would be >>> OK to bump Jenkins' runtime dependency from Java5 to Java6. >>> The core is already build on Java6, but until now still backward >>> compatible with Java5. >>> Therefore we would like to know from you (Users) whether you have an >>> issue with this upgrade. >>> This would mean, that in the future you will have to have Java6 >>> installed to run Jenkins (for Master and Slave). >>> >>> Here are the current usage numbers (installations we know of): >>> Java 1.5: 655 >>> Java 1.6: 29164 >>> Java 1.7: 2919 >>> >>> So please give us some feedback/votes on this. >>> Domi >>> >>> >>> >> >> -- >> Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ >> Try Nectar, our professional version of Jenkins >> > > -- 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/groups/opt_out.
