> Didn't you just configured a JDK installation and select it from your job > configuration ? Ya. Once I know how that works. I didn't expect it to be a global jenkins configuration when I only have that setup on a single slave. Maybe I am a bit slow. I also configured the slave to start with the desired jdk and was surprised when the job didn't use that same slave.
But we shouldn't stay at Java6 forever. I am seeing a lot of hints at making some radical changes/improvements. Should we really be talking of a Jenkins2 and not expect people to auto-update to it? We could offer 1 or 2 more LTS on the 1.x track. What would change in 3/ 6 months ? Lot's of people will still run RHEL 5 and build legacy Java 1.3 applications. Ok, maybe 10 LTS's then. We need to have a plan for supporting the past and the future. If we do have so many people wanting the java6 branch, then they should be able to support it. It sounds like we have a large number of people interested in java8 and I don't think such a transition will be ready for quite some time. I imagine we will also have people using both and maintaining both. I still have RHEL5 and a SPARC and I will do what I have to with those as long as I need to. But I also have bleeding edge items and I'd like to see Jenkins continue to push that envelope. This is a community, I can't imagine that if the mainline moved on to Java8 we wouldn't still help those who are still using the current mainline. - Thomas -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D13733B8.11501%25thomas.suckow%40pnnl.gov. For more options, visit https://groups.google.com/d/optout.
