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

Reply via email to