+1
On Wed, Feb 28, 2024 at 8:31 AM Benjamin Marwell
wrote:
> Hi Maven Devs/Users/Committers and PMC members!
>
> After several discussions on the mailing lists, I would like to
> start a vote in favour of setting the minimal Java bytecode target
> of Maven-Core 4 to 17 and hence require Java 17
Hi all,
the vote has passed with the following result:
PMC +1: Anders Hammar, Arnaud Héritier, Benjamin Marwell, Guillaume
Nodet, Hervé Boutemy, Karl Heinz Marbaise, Konrad Windszus, ,Maarten
Mulders, Olivier Lamy, Romain Manni-Bucau, Sylwester Lachiewicz, Tamás
Cservenák
PMC majority quorum:
+1
On Wed, Feb 28, 2024, 08:31 Benjamin Marwell wrote:
> Hi Maven Devs/Users/Committers and PMC members!
>
> After several discussions on the mailing lists, I would like to
> start a vote in favour of setting the minimal Java bytecode target
> of Maven-Core 4 to 17 and hence require Java 17 for
+1
On Wed, Feb 28, 2024 at 2:32 AM Benjamin Marwell wrote:
>
> Hi Maven Devs/Users/Committers and PMC members!
>
> After several discussions on the mailing lists, I would like to
> start a vote in favour of setting the minimal Java bytecode target
> of Maven-Core 4 to 17 and hence require Java
I've staged release candidates for maven-filtering-3.3.2 and
maven-remote-resources-plugin-3.2.0 at
https://repository.apache.org/content/repositories/maven-2067
JIRA release notes:
https://issues.apache.org/jira/projects/MSHARED/versions/12353084
You should be able to use @code in same way now without the java upgrade.
*
* {@code
*
* -Xmaxerrs
* 1000
* -Xlint
* -J-Duser.language=en_us
*
* }
*
Something like that anyways and all the ugly escapes can go now.
+1
sob., 2 mar 2024, 10:48 użytkownik Guillaume Nodet
napisał:
> I've staged release candidates for maven-filtering-3.3.2 and
> maven-remote-resources-plugin-3.2.0 at
> https://repository.apache.org/content/repositories/maven-2067
>
> JIRA release notes:
>
Just realized since I'm working on the Maven compiler plugin, upgrading
to Java 21 instead of 17 would allow us to replace currently
hard-to-read Javadoc like this:
*
* compilerArgs
* arg-Xmaxerrs/arg
* arg1000/arg
* arg-Xlint/arg
*
I don't see any blockers with either of these. However, the
maven-remote-resources-plugin repo is currently broken because it
depends on the new maven-filtering. I would prefer to vote on and
release maven-filtering-3.3.2 and only then vote on and release
maven-remote-resources-plugin-
3.2.0.
On
Le 2024-03-02 à 18 h 55, Jeremy Landis a écrit :
You should be able to use @code in same way now without the java upgrade.
Yes I know. But Maven source code currently uses , and if we were
to spent an effort for changing that, it would have been more economical
to go directly to {@snippet}
10 matches
Mail list logo
