no need to change the build prerequisite: just add a profile to activate the
release flag on newer JDK:
https://issues.apache.org/jira/browse/MPOM-447
Regards,
Hervé
Le lundi 13 novembre 2023, 20:38:00 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> currently we have already the build
I'm OK with Java 11 required to build Maven in 2023, but I'll play my
broken record: it is not yet OK to require Java 11 to run Maven or
plugins.
There are still a lot of developers out there who are using JDK 8
toolchains. and contrary to common claims, it is still a supported
version by many
+1 (non-binding)
Actually, it should not make any difference if one builds a plugin using
Java 11 or Java 17 (or even Java 21 with a warning) and targets Java 8
using the "--release 8" option (and that dependencies are compatible), so
just for using --release option is actually enough (even if
Not my week. Need to cancel this one as well. One issue is missing.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
oh right, sorry I didn't read correctly.
Do you want to build with Java 11 as a minimum but limit to the usage of Java 8?
What is the point?
We (as Maven developers) will have to use Java 11 to build plugins but
not be able to use Java 11 features in the code.
That sounds frustrating to me :)
Or I
+1
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
On 14.11.23 12:54, Elliotte Rusty Harold wrote:
I'm OK with Java 11 required to build Maven in 2023, but I'll play my
broken record: it is not yet OK to require Java 11 to run Maven or
plugins.
There are still a lot of developers out there who are using JDK 8
toolchains. and contrary to
Hi,
On 14.11.23 14:16, Hervé Boutemy wrote:
no need to change the build prerequisite: just add a profile to activate the
release flag on newer JDK:
https://issues.apache.org/jira/browse/MPOM-447
Add another profile...
it would be better to clean up those things and make clean upgrade
Guys,
please take moment to cast your vote. One day left.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
+1
On Sun, Nov 12, 2023 at 7:59 PM Michael Osipov wrote:
> Hi,
>
> we solved 2 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353749
>
> There are no issues left in JIRA:
>
>
+1
W dniu wt., 14.11.2023 o 20:27 Tamás Cservenák
napisał(a):
> +1
>
> On Sun, Nov 12, 2023 at 7:59 PM Michael Osipov
> wrote:
>
> > Hi,
> >
> > we solved 2 issues:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353749
> >
> > There are no issues left in
+1
There's not much in this release, mostly the parent upgrade. What's
the expectation here ?
Le dim. 12 nov. 2023 à 19:59, Michael Osipov a écrit :
>
> Hi,
>
> we solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353749
>
> There are no issues left
> We (as Maven developers) will have to use Java 11 to build plugins but
> not be able to use Java 11 features in the code.
> That sounds frustrating to me :)
> Or I don't understand the change you are trying to propose?
Not at all. This is how I did it at work.
This already removes a lot of
13 matches
Mail list logo
