All active components already are compatible with Java 8 (except one maybe).
Gary On Wed, May 31, 2023, 15:29 Glavo <zjx001...@gmail.com> wrote: > Java 8 jars can include module-info.class even if they are not > multi-release. > Java 8 does not load module-info.class, so there is no need to use MR for > isolation. > > I hope to make our components compatible with Java 8 for 2-4 years. > During this period, we can compile module-info.java separately and package > it into a jar. > Now there is a maven plugin[1] that can help us complete this task. > > When Project Valhalla arrives (maybe Java 25), it will bring huge changes > to the Java ecosystem. > At that time, we can refactor all components based on value classes[2] and > universal generics[3], > making them faster, easier to use and more modern. > > Glavo > > [1]: https://github.com/moditect/moditect > [2]: https://openjdk.org/jeps/8277163 > [3]: https://openjdk.org/jeps/8261529 > > On Thu, Jun 1, 2023 at 2:50 AM Gary Gregory <garydgreg...@gmail.com> > wrote: > > > I prefer to lead a simpler life Matt ;-) > > > > MR jars are an abomination IMO. > > > > Gary > > > > On Wed, May 31, 2023, 11:51 Matt Sicker <m...@musigma.org> wrote: > > > > > How about using multi-release jars? That way we can include module-info > > > files and version-specific additions while still supporting Java 8 for > a > > > while. It could require a newer Java compiler while still targeting the > > > Java 8 bytecode version. > > > — > > > Matt Sicker > > > > > > > On Apr 23, 2023, at 08:46, 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 > > > > > > > > >