Le sam. 23 juil. 2022 à 17:25, Benjamin Marwell <bmarw...@apache.org> a
écrit :
> No, 2 JDKs are not required by default. Only if you use --release={<17} and
> don't trust running tests on 17 are the same as running tests on 8.
> Yes, there are changes (certificates, XML libs, rhino, etc).
>
As explained it means you dont write a single test or dont care of the test
results so yes it needs 2 jdk.
> So, for most projects that's probably not needed. For those who think it is
> needed, I don't have a lot of pity. But it will be a requirement for quite
> a few commercial projects, like Containers (JavaEE, as they will need to be
> Java 8 as long as 2030ish due to extended support contracts).
>
> That said, I'm still thinking Java 17 will be a sane default.
>
>
> On Sat, 23 Jul 2022, 10:50 Delany, <delany.middle...@gmail.com> wrote:
>
> > Using mvnd with toolchains doesn't improve the situation, in fact
> > toolchains seem to invalidate any benefit of using mvnd.
> > Even if this was resolved, is it fair to require mvnd?
> > Delany
> >
> >
> > On Sat, 23 Jul 2022 at 10:17, Mark Derricutt <m...@talios.com> wrote:
> >
> > > Is that due to cold starting the JVM each time?
> > >
> > > I wonder if mvnd supports toolchains effectively? Or if that could be
> an
> > > avenue to try.
> > > --
> > > "Great artists are extremely selfish and arrogant things" — Steven
> > Wilson,
> > > Porcupine Tree
> > >
> > > On 23/07/2022 at 8:13:23 PM, Delany <delany.middle...@gmail.com>
> wrote:
> > >
> > > > I tried toolchains but dropped it because of the exorbitant
> performance
> > > > costs.
> > > > A multi-module build that normally built in 3:50 took 10:34, and
> that's
> > > > with toolchaining only maven-compiler-plugin.
> > > >
> > > >
> > > >
> > >
> >
>
