I think you can make the release with JDK8 since that's consistent with past releases.
On Fri, Jun 28, 2019 at 4:17 PM Sutou Kouhei <k...@clear-code.com> wrote: > > Thanks Wes! > > I'm still waiting for comments from Java developers. > > -- > kou > > In <cajpuwmdeozrzudf-8_tyhvztrwo+_ugghkduexl8re3hw-n...@mail.gmail.com> > "Re: 0.14.0: Javadoc failed with OpenJDK 11" on Thu, 27 Jun 2019 16:40:44 > -0500, > Wes McKinney <wesmck...@gmail.com> wrote: > > > hi Kou, > > > > I think that JDK8 is still treated as the "main production JDK > > version" but based on > > > > https://blogs.oracle.com/java-platform-group/end-of-public-updates-is-a-process%2c-not-an-event > > > > it seems like the project should cease JDK8 support at some point in > > the next 18 months (or sooner). I think it is OK to make the release > > using JDK8 > > > > I will let the Java stakeholders comment about what they want to do. > > There are still a few patches that need to be merged until the RC0 so > > there is a bit of time yet. Hopefully we can have everything resolved > > within the next 12 hours > > > > Thanks, > > Wes > > > > On Thu, Jun 27, 2019 at 4:24 PM Sutou Kouhei <k...@clear-code.com> wrote: > >> > >> Hi, > >> > >> I'm trying to run dev/release/00-prepare.sh that is the > >> first script to create RC. > >> > >> It fails with OpenJDK 11 by the following Javadoc error: > >> > >> [ERROR] Exit code: 1 - javadoc: error - The code being documented uses > >> modules but the packages defined in > >> http://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. > >> > >> "-source 8" javadoc option can suppress the error but I'm > >> not sure what should we do. > >> > >> See also: https://issues.apache.org/jira/browse/ARROW-5764 > >> > >> I found that OpenJDK 8 doesn't cause the error. So I can go > >> ahead with OpenJDK 8. But I want feedback from Java > >> developers to know we should use OpenJDK 8 for release. > >> > >> > >> Thanks, > >> -- > >> kou
