Re: [DISCUSS] Drop Java 8 support

e to keep doing that if possible. Our clients are big > > > >> enterprises > > > >> > > > with > > > >> > > > >> notoriously sluggish update cycles, so we want to offer > > maximum > > > >> > > > >&

Re: [DISCUSS] Drop Java 8 support

; > >> > projects > > > > > >> > > to > > > > > >> > > > > drop Java <17? How did they weigh the benefits/drawbacks > > for > > > > > >> dropping > > > > > >> > >

Re: [DISCUSS] Drop Java 8 support

t; > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > On Tue, Apr 30, 2024 at 4:14 PM < > martin.trave...@icloud.com > > > >

Re: [DISCUSS] Drop Java 8 support

ng that if possible. Our clients are big > > > >> enterprises > > > >> > > > with > > > >> > > > >> notoriously sluggish update cycles, so we want to offer > > maximum > > > >> > > > >> compati

Re: [DISCUSS] Drop Java 8 support

ally > > >> > > follow > > >> > > > >> the EOL schedule of our dependencies. > > >> > > > >> > > >> > > > >> Corretto, Adoptium and Zulu all have recent public builds of > > >> both 8

Re: [DISCUSS] Drop Java 8 support

gt;> Oracle > >> > > when > >> > > > >> they made their licensing blunder with Java 8 and although that > >> is > >> > > > >> rectified now, the change seems to have stuck in quite a few > >> places > >> >

Re: [DISCUSS] Drop Java 8 support

t; > > > applications >> > > > >> then perhaps most people have figured out by now to add the JVM >> > params >> > > > that >> > > > >> let Java continue working. Still, it could be a consideration, if >> > > > Java1

Re: [DISCUSS] Drop Java 8 support

> take so > > > > >> long with that, even C++ got there sooner! > > > > >> > > > > >>> On 30 Apr 2024, at 16:20, Jacob Wujciak > > > wrote: > > > > >>> > > > > >>> Hello everyone! > > > > >>

Re: [DISCUSS] Drop Java 8 support

t move to 11 and then have the pain of > > > migration > > > >>> again when we drop that (which will happen soon regardless imo). > > > >>> > > > >>> Am Di., 30. Apr. 2024 um 16:18 Uhr schrieb Dane Pitkin > > > >>>

Re: [DISCUSS] Drop Java 8 support

Apache Spark jumped straight to > Java > > >> 17. > > >>>> It seems other projects are dropping both 8 and 11 at the same time > as > > >>>> mentioned by Fokko. From a maintenance perspective, it would be nice > > to > > >>&g

Re: [DISCUSS] Drop Java 8 support

ce > to > >>>> drop both. > >>>> > >>>> On Mon, Apr 29, 2024 at 11:20 AM Jean-Baptiste Onofré < > j...@nanthrax.net> > >>>> wrote: > >>>> > >>>>> Hi > >>>>> > >>>>> I think i

Re: [DISCUSS] Drop Java 8 support

ng directly to Java17 would be problematic >>>>> potentially for some users I guess). >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> On Thu, Apr 25, 2024 at 10:21 PM James Duong >>>>> wrote: >>>>>

Re: [DISCUSS] Drop Java 8 support

could use the JDK to compile module-info.java > > > > files. Then we could remove the custom maven plugin we’re using for > > > > compiling module-info.java files for JPMS support and get better IDE > > > > integration (as what we’re doing currently somewhat sho

Re: [DISCUSS] Drop Java 8 support

e-info.java files for JPMS support and get better IDE > > > integration (as what we’re doing currently somewhat shoe-horns module > > > information alongside JDK8 bytecode). > > > > > > > > From: Dane Pitkin > > > > Date: Thursday, April 25, 2024 at

Re: [DISCUSS] Drop Java 8 support

files. Then we could remove the custom maven plugin we’re using for > > compiling module-info.java files for JPMS support and get better IDE > > integration (as what we’re doing currently somewhat shoe-horns module > > information alongside JDK8 bytecode). > > > >

Re: [DISCUSS] Drop Java 8 support

> >>>> > >>>> If we dropped JDK 8, we could use the JDK to compile module-info.java > >>> files. Then we could remove the custom maven plugin we’re using for > >>> compiling module-info.java files for JPMS support and get better IDE > >>

Re: [DISCUSS] Drop Java 8 support

>>> >>>> If we dropped JDK 8, we could use the JDK to compile module-info.java >>> files. Then we could remove the custom maven plugin we’re using for >>> compiling module-info.java files for JPMS support and get better IDE >>> integration (as wh

Re: [DISCUSS] Drop Java 8 support

es. Then we could remove the custom maven plugin we’re using for > > compiling module-info.java files for JPMS support and get better IDE > > integration (as what we’re doing currently somewhat shoe-horns module > > information alongside JDK8 bytecode). > > > > > >

Re: [DISCUSS] Drop Java 8 support

DE > integration (as what we’re doing currently somewhat shoe-horns module > information alongside JDK8 bytecode). > > > > From: Dane Pitkin > > Date: Thursday, April 25, 2024 at 1:02 PM > > To: dev@arrow.apache.org > > Subject: [DISCUSS] Drop Java 8 support

Re: [DISCUSS] Drop Java 8 support

gt; From: Dane Pitkin > Date: Thursday, April 25, 2024 at 1:02 PM > To: dev@arrow.apache.org > Subject: [DISCUSS] Drop Java 8 support > Hi all, > > I would like to revisit the discussion of dropping Java 8 (and maybe 11) > from Arrow's Java implementation. See GH issu

Re: [DISCUSS] Drop Java 8 support

Thanks James, Fokko! Sounds like we are generally in agreement to move forward. I'll leave the discussion open for now in case others have questions/comments to add. On Thu, Apr 25, 2024 at 4:25 PM Fokko Driesprong wrote: > Hey Dane, > > Thanks for bringing this up again. > > In the dev-list th

Re: [DISCUSS] Drop Java 8 support

Hey Dane, Thanks for bringing this up again. In the dev-list thread you referred to I hesitated to drop Java <17, but it is time. We see several projects that are moving past Java 8, and in the process are also dropping Java 11 since it is not supported anymore

Re: [DISCUSS] Drop Java 8 support

alongside JDK8 bytecode). From: Dane Pitkin Date: Thursday, April 25, 2024 at 1:02 PM To: dev@arrow.apache.org Subject: [DISCUSS] Drop Java 8 support Hi all, I would like to revisit the discussion of dropping Java 8 (and maybe 11) from Arrow's Java implementation. See GH issue[1] below. This was

[DISCUSS] Drop Java 8 support

Hi all, I would like to revisit the discussion of dropping Java 8 (and maybe 11) from Arrow's Java implementation. See GH issue[1] below. This was also discussed in the last Arrow community sync meeting on 2024-04-24. For context, this was discussed[2] last year on this mailing list. We decided t