This sounds harmless, although since JDK8 remains the maximum version to
compile Geode, this mean anyone that wants build both geode and geode-examples
will now have to install multiple JDKs and flip back and forth between. And
how will geode-examples composite builds work, where geode and geod
@alexander, I agree that stabilizing on 1.14 will be much easier to do, than to
manage the fixes while develop features move along apace. I disagree that
shifting attention to 1.14 will mean that develop does not get better. We can
port the fixes forward, just as easily as we backport them. Same
Hi all,
Thanks, Owen for reminding us all of this topic!
I wonder how we feel about the state of develop right now. If we cut 1.14 right
now, it will make it easier to stabilize and ship it. However, I see 21 open
JIRA tickets affecting 1.14.0. It might be better to have an all-hands effort
to
A contributor submitted a PR[1] to our geode examples project that uses Java 11
APIs. It doesn't pass travis because we're still building the examples with
Java 8.
I think it might be reasonable to switch the minimum java version of the
examples to Java 11. If there are no objections, I'll go a
