RE: [VOTE] Require Java 17 for Maven 4

[Jeremy Landis]

You should be able to use @code in same way now without the java upgrade.

      * <pre>
      * {@code
      * <compilerArgs>
      *   <arg>-Xmaxerrs</arg>
      *   <arg>1000</arg>
      *   <arg>-Xlint</arg>
      *   <arg>-J-Duser.language=en_us</arg>
      * </compilerArgs>
      * }
      * </pre>

Something like that anyways and all the ugly escapes can go now.

-----Original Message-----
From: Martin Desruisseaux <martin.desruisse...@geomatys.com> 
Sent: Saturday, March 2, 2024 11:55 AM
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: [VOTE] Require Java 17 for Maven 4

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:

      * <pre>
      * &lt;compilerArgs&gt;
      *   &lt;arg&gt;-Xmaxerrs&lt;/arg&gt;
      *   &lt;arg&gt;1000&lt;/arg&gt;
      *   &lt;arg&gt;-Xlint&lt;/arg&gt;
      *   &lt;arg&gt;-J-Duser.language=en_us&lt;/arg&gt;
      * &lt;/compilerArgs&gt;
      * </pre>

by:

      * {@snippet lang="xml" :
      * <compilerArgs>
      *   <arg>-Xmaxerrs</arg>
      *   <arg>1000</arg>
      *   <arg>-Xlint</arg>
      *   <arg>-J-Duser.language=en_us</arg>
      * </compilerArgs>
      * }

However it may not a sufficient reason for restarting a new vote. I'm just 
mentioning that for info.

     Martin