Exactly.  I think at major version cuts, we should drop support for JDKs
that are no longer supported [1].  Part of that is simply availability of
JDKs to test against and the implied commitment to do that testing and fix
bugs that may be JDK-specific.  Part of it is to allow use of new language
features.  We only have this opportunity once - when we start the new major
version - and IMO we should always take it.

Phil

[1] That is getting a little trickier now with LTS.

On Wed, Jul 19, 2023 at 2:42 PM Gary Gregory <garydgreg...@gmail.com> wrote:

> The simplest way to bake in JPMS automatically is to build with the
> Moditect plugin and Java 11.
>
> There is also an expectation from new contributors that current development
> does not happen on the dead and EOL Java 8. It will be nice to at least
> have the option to use new language features and APIs.
>
> This is a major release and the perfect and expected time to bump Java
> versions IMO.
>
> Gary
>
>
> On Wed, Jul 19, 2023, 17:21 Alex Herbert <alex.d.herb...@gmail.com> wrote:
>
> > On Wed, 19 Jul 2023 at 19:38, Gary Gregory <garydgreg...@gmail.com>
> wrote:
> > >
> > > OK, that sounds good.
> > >
> > > Gary
> > >
> > > On Tue, Jul 18, 2023 at 5:50 PM Phil Steitz <phil.ste...@gmail.com>
> > wrote:
> > > >
> > > > I would say 17 for 3.0.
> > > >
> > > > Phil
> >
> > Are there aspects of Pool that require moving away from JDK 8? Such a
> > move would restrict downstream consumers of the library.
> >
> > Alex
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >
>

Reply via email to