On Tue, Aug 31, 2021 at 9:58 AM Ivan Kelly wrote:
> > * Pulsar client should remain on JDK 8
> I'm sure this was discussed in the past, but who is the JDK8 support
> being maintained for?
> And wouldn't they just continue to use the 2.8 client which does support 8?
The effort required to switch
> My doubt here is if that alone is enough of a reason to require users
> to switch, or if we should instead wait for JDK 17 and fast track to
> that.
The biggest thing isn't to get people on to a new one. It's to wean
them off of jdk8. jdk11 achieves this.
-Ivan
On Tue, Aug 31, 2021 at 9:52 AM Jonathan Ellis wrote:
>
> Well, it's 9+10+11, so the big one is local type inference from Java 10.
Yes, local type inference is nice, but it's definitely not game
changing. (eg: if we could use something like value types or
green-threads, we could use that to impro
> * Pulsar client should remain on JDK 8
I'm sure this was discussed in the past, but who is the JDK8 support
being maintained for?
And wouldn't they just continue to use the 2.8 client which does support 8?
-Ivan
Well, it's 9+10+11, so the big one is local type inference from Java 10.
On Tue, Aug 31, 2021 at 11:12 AM Matteo Merli wrote:
> The discussion in the past was around these points:
> * Pulsar client should remain on JDK 8
> * We could move server modules to JDK 11 for Pulsar 2.9
> * After JDK
The discussion in the past was around these points:
* Pulsar client should remain on JDK 8
* We could move server modules to JDK 11 for Pulsar 2.9
* After JDK 17 is out for > 6 months, consider moving server modules to 17
The question, right now, is what "source level" features are we
missing f
> Sorry for not being clear. My question is, when do we start requiring
> JDK11+ so that we can start using newer Java features in the Pulsar code
> base?
I think this is using jdk11+ for the build and the broker should be fine.
The client, and modules depended on by the client may be a different
Sorry for not being clear. My question is, when do we start requiring
JDK11+ so that we can start using newer Java features in the Pulsar code
base?
On Tue, Aug 31, 2021 at 9:23 AM Enrico Olivelli wrote:
> Jonathan,
> Pulsar 2.8 (and 2.9) builds well on JDK8 and JDK11.
> Tests are passing.
> De
Jonathan,
Pulsar 2.8 (and 2.9) builds well on JDK8 and JDK11.
Tests are passing.
Developers can use both JDK8 and JDK11.
CI is running ONLY on JDK11 and we have a single workflow that runs some
tests on JDK8.
The binary tarballs work with JDK8 and JDK11
The Java client works with JDK8 and JDK11
Th
What is the plan to fully move to JDK 11 (or JDK 17 which will be released
as LTS in two weeks)?
I remember Enrico starting a thread in February but I haven't seen an
update since then.
On Tue, Aug 31, 2021 at 5:15 AM Hang Chen wrote:
> Hello Apache Pulsar Community,
> In Apache Pulsar 2.8.
10 matches
Mail list logo
