Sdkman is also a good option (and avoids binaries in sources)
That said, cant plugin check out they work?
It does not sound hard to check java version/parameters/... and validate
that when creating a mojo, isnt it?
Le mar. 29 oct. 2019 à 19:46, Robert Scholte a
écrit :
> One of the
One of the fundamental features of Maven is Convention Over Configuration, in
other words: define defaults where possible, but make it possible to change
these values.
However, "default" can be explained differently, either as constant (forever)
or as a predefined value within a certain
Le mar. 29 oct. 2019 à 14:24, Enrico Olivelli a
écrit :
> Il giorno mar 29 ott 2019 alle ore 14:22 Stephen Connolly <
> stephen.alan.conno...@gmail.com> ha scritto:
>
> > Because maintaining Java 7 is a barrier to new contributors. It is tricky
> > enough to get Java 8 set up for some
Il giorno mar 29 ott 2019 alle ore 14:22 Stephen Connolly <
stephen.alan.conno...@gmail.com> ha scritto:
> Because maintaining Java 7 is a barrier to new contributors. It is tricky
> enough to get Java 8 set up for some developers. Every version we support
> adds complexity for contributors.
019 um 14:21 Uhr
> Von: "Stephen Connolly"
> An: "Maven Developers List"
> Betreff: Re: Re: [DISCUSS] Maven 3.7.0
>
> Because maintaining Java 7 is a barrier to new contributors. It is tricky
> enough to get Java 8 set up for some developers. Every version we s
Because maintaining Java 7 is a barrier to new contributors. It is tricky
enough to get Java 8 set up for some developers. Every version we support
adds complexity for contributors. Personally, I think we should be thinking
about dropping even Java 8 if we wait until next year and just follow the
Why not have 3.7.0 plugin updates and other non-technical stuff, have it
parallely maintained for some time and move with Maven 3.8.0 to Java 8 next
year?!
Does that sound like a plan? I'd be happy with that. I'd also expect
an announcement on dev@, announce@ and users@.
Michael
> Gesendet:
