The primary reason for moving to Java 11 is to fully support JPMS. Most libraries have added an automatic module name to the Manifest but that doesn’t really make it fully JPMS enabled.
To be honest, the number of people I’ve seen asking for full JPMS support is quite small though. Ralph > On Apr 23, 2023, at 10:10 AM, Glavo <zjx001...@gmail.com> wrote: > > I don't think upgrading to Java 11 is a very attractive proposition. > There are not many language features introduced in Java 9~11, > so there are not enough benefits to upgrade to Java 11. > > The lifecycle of Java 11 is much shorter than that of Java 8. > Premier support for Java 11 will end this year, and the extended support > will > also end in 2026, but Java 8 will be supported until 2030. > > I think if we want to stop supporting Java 8, then we have no reason to > continue > supporting Java 11. We can skip Java 11 and use Java 17. > > Next, we can prepare for Java 25, as Project Valhalla may be waiting for us > there. > > Glavo > > On Sun, Apr 23, 2023 at 9:47 PM Gary Gregory <garydgreg...@gmail.com> wrote: > >> Hi All, >> >> In the year 2023, and with Java 21 in EA (https://jdk.java.net/21/), I >> think it is time to start migrating our components from Java 8 to Java >> 11. I imagine this to happen slowly and surely over the course of this >> whole year. >> >> In addition, originally, it should also be time to update our GitHub >> builds to run on Java 21-EA. >> >> Gary >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
