Quite frankly I wouldn't bother with a JDK 8 upgrade. JDK 8 is not 100% backwards compatible despite what Oracle says and IMHO the last bits of code in gate that rely on java should be gutted or rewritten.
Here is what I would do: stick to KYSTY by eventually upgrading to the latest OpenJDK 7 and telling users to install their own JDK if they want to use java as at some time in the future, OpenJDK won't be bundled anymore. On Thu, Nov 12, 2015 at 5:08 PM, Eric Sproul <eric.spr...@circonus.com> wrote: > On Thu, Nov 12, 2015 at 10:29 AM, Dan McDonald <dan...@omniti.com> wrote: >> >>> On Nov 12, 2015, at 7:20 AM, Ben Summers <b...@fluffy.co.uk> wrote: >>> >>> And that's why I don't think it's possible to use the built in one for >>> anything. Are you committing to getting a Java update out the same day as >>> Oracle? >> >> That's an excellent point. I'm not. >> >> Given that the built-in java is only used for poold, perhaps I should spend >> my time elsewhere. I'm also running into openjdk8 doing things >> new&differently that REALLY mess up existing assumptions in build.sh. :) > > The Java landscape is also confusing as heck these days, given Oracle > Java SE vs. OpenJDK. *Oracle* is no longer publicly updating Java SE > 7, but *OpenJDK* 7 appears to still be getting updates, but I've been > unable to locate any sort of end date for OpenJDK's "jdk7u" project. > I guess this means that security updates will still come out for > OpenJDK 7? > > Eric > _______________________________________________ > OmniOS-discuss mailing list > OmniOS-discuss@lists.omniti.com > http://lists.omniti.com/mailman/listinfo/omnios-discuss _______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
