@jshaffer2112 et al, happy to get opinions on moving Cloud to JVM 11, been wanting to do that for a while. Anybody see downsides?
I'm with John on this. If it was a reversible flag in case some lib doesn't work, that would add a lot of confidence when trying this migration
Just chiming in here -- I am in favor of moving Cloud for JVM 11. We are still in early stages of our product and the conversion won't be that painful.
The only change we had to make when moving from 8 -> 11 was adding --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED to our jvm opts for Neanderthal. Everything else has been exactly the same. It’s been nice to have access to the built in http client and some of the newer date methods, like the one John referred to, without needing to wrap them.
Can it start as a stack parameter for the JVM version? That would give people plenty of time to work out issues like kenny's