Re: JMPS support, proposal 3

2024-01-13 Thread Romain Manni-Bucau
Afaik the ci is up to date so must pass so likely needs a fix. Le sam. 13 janv. 2024 à 14:43, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit : > Just saw that the CI build has been successful on Java 17 and 21, but > failed on Java 11 because of the use of the |{@return ...}|

Re: [VOTE] Release Apache Maven 4.0.0-alpha-12

2024-01-13 Thread Slawomir Jaranowski
+1 pt., 12 sty 2024 o 11:45 Guillaume Nodet napisał(a): > I'm starting a new vote to release this new alpha. > This release brings the latest Maven Resolver 2.0.0-alpha-6, leveraging > artifact collection filtering and the new transitive dependency manager. > JLine has been leveraged to provide

Re: [VOTE] Release Apache Maven 4.0.0-alpha-12

2024-01-13 Thread Sylwester Lachiewicz
+1 Sylwester pt., 12 sty 2024 o 14:28 Tamás Cservenák napisał(a): > +1b > > tested on several local projects I have checked out, works good > > T > > On Fri, Jan 12, 2024 at 11:44 AM Guillaume Nodet > wrote: > > > I'm starting a new vote to release this new alpha. > > This release brings the

Re: JMPS support, proposal 3

2024-01-13 Thread Martin Desruisseaux
Just saw that the CI build has been successful on Java 17 and 21, but failed on Java 11 because of the use of the |{@return ...}| javadoc tag. This is a trivial Javadoc issue only. Its resolution depends on Maven PMC decision about which Java version to require.     Martin

Re: JMPS support, proposal 3

2024-01-13 Thread Martin Desruisseaux
Le 2024-01-10 à 15 h 01, Tamás Cservenák a écrit : IMO, add all. I think is fine, but PR discussion will decide anyway... Created a JIRA task [1] and a pull request [2] after rebasing behind latest Maven commit. Note 1: the guideline shown when creating the pull request suggested to put the