Re: Upgrading Java version in build toolchain

2024-06-25 Thread Laurent Goujon
I'm still working on this and have created a WIP pull request to demonstrate the list of changes: https://github.com/apache/arrow/pull/43050 Laurent On Mon, May 6, 2024 at 9:40 AM Laurent Goujon wrote: > I wanted to share some status updates: I do have a list of changes to > build Arrow with a

Re: Upgrading Java version in build toolchain

2024-05-06 Thread Laurent Goujon
I wanted to share some status updates: I do have a list of changes to build Arrow with a recent version of Java using the `--release` plugin option of javac. The full change is available at: https://github.com/laurentgo/arrow/pull/3 Here are roughly how the changes are divided: * Change access to

Re: Upgrading Java version in build toolchain

2024-04-10 Thread Laurent Goujon
I can give it a try for sure On Fri, Apr 5, 2024 at 10:26 AM Dane Pitkin wrote: > I think we can revisit the discussion soon for dropping Java 8 altogether, > since Spark will release 4.0 in ~June supporting Java 17+ at runtime. > > I'm curious how big of an effort it would be to get your propos

Re: Upgrading Java version in build toolchain

2024-04-05 Thread Dane Pitkin
I think we can revisit the discussion soon for dropping Java 8 altogether, since Spark will release 4.0 in ~June supporting Java 17+ at runtime. I'm curious how big of an effort it would be to get your proposal implemented. Would you be willing to draft a PR so we can see what types of changes are

Re: Upgrading Java version in build toolchain

2024-04-03 Thread Jean-Baptiste Onofré
Yes, correct for language features. My point was more that we can decide on a major Arrow version upgrading the target language version. That's what I meant by "consensus". Regards JB On Tue, Apr 2, 2024 at 5:55 PM Laurent Goujon wrote: > > At code level we need to separate language features fro

Re: Upgrading Java version in build toolchain

2024-04-02 Thread Laurent Goujon
At code level we need to separate language features from library features? It should be possible to leverage memory API for example through reflection and/or multi-release jar files, but record is a language feature and it would not possible to use it without targeting java 17 at the source level.

Re: Upgrading Java version in build toolchain

2024-04-02 Thread Jean-Baptiste Onofré
Hi Laurent It makes sense to me. I started this "move" (on the plugin side of the thing) as part of the reproducible build effort. At code level, I think it would be great to leverage some features from Java 17+ (I'm thinking about record, memory API, etc). I would be more than happy to help on t