I suppose so, I guess just highlighting that we shouldn't bother dedicating
much testing resources to 4.0 on 11.
I will note however that if we wanted to start making changes to support 11
it'd have to be (as Robert alluded to) based off an incomplete 11 as I'm
assuming we'd make no further
That's probably not far off what Robert suggested:
"The idea here is to default to Java 8, but the code also runs on 11"
"Initially, only the combination of C* 4.0 + Java 8 would be labeled as
"stable" and the combination of C* 4.0 + Java 11 as "experimental"."
If Robert wants to go ahead
Hi Roman,
I was able to reproduce the issue you described. I filed
https://issues.apache.org/jira/browse/CASSANDRA-14479. More details there.
Thanks for reporting!
Jordan
On Wed, May 23, 2018 at 12:06 AM, Roman Bielik <
roman.bie...@openmindnetworks.com> wrote:
> Hi,
>
> I apologise for a
So for anyone that missed it, Java 11 will be released in September 2018.
I'd prefer we target one Java release only. This is purely because we don't
have the capacity or capability to test both releases. We hardly do a good
enough job as it is of testing and lumping another JVM into the mix is
