Hi Thomas, I was able to do a full build with the changes to tests provided in https://issues.apache.org/jira/browse/SSHD-1347?focusedCommentId=18031229&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-18031229.
May I suggest a new RC? Gary On Wed, Oct 22, 2025 at 7:35 AM Christoph John <[email protected]> wrote: > > Hi, > > sorry for jumping in: what about using Maven Wrapper > https://maven.apache.org/tools/wrapper/ to prevent the Maven version troubles? > > Cheers > Chris > > -- > Christoph John > Software Engineering > > D +49 241 557080 28 > [email protected] > > > > MACD GmbH > Oppenhoffallee 103 > 52066 Aachen, Germany > www.macd.com > > > > Amtsgericht Aachen: HRB 8151 > Ust.-Id: DE 813021663 > Geschäftsführer: George Macdonald und Florian Festner > > -----Original Message----- > From: Emmanuel Lecharny <[email protected]> > Sent: 22 October 2025 05:59 > To: [email protected] > Subject: Re: [VOTE] Milestone Pre-Release Apache MINA SSHD 3.0.0-M2 > > Thanks Thomas! > > I get it about Java version. And also see where you are coming from with > Maven, accordingly to your Java 24 requirement, that now makes complete sense. > > I was still using an older version of both (Java 21 and Maven 3.6), so I had > to download and install both on my machines (plus a few tweaks to get them > used), that why it took me half an hour. But now it's settled so all is ok. > > Anyway, for the first time I was able to build the code without any issue > (like even without having Docker desktop running!) and even if it took a > while, I had a working build. > > I still have to understand why the build is stopping many times on my Ubuntu > machine (not the case on Mac OS), like 9 times. I had to restart the build up > to the point it was stopped (using fg). A tad annoying, but not a big deal > beside the mystery... > > > Thanks a lot for the explanation and for the good work with the release! > > > On 10/20/25 20:06, Thomas Wolf wrote: > > On 20.10.25 11:00, Emmanuel Lecharny wrote: > >> Hi! > >> > >> I would have expected Java 25 to have been the required JVM version, > >> and not 24, which is an intermediary version. I wonder why Java 21 is > >> not the requested version though. > > > > The minimal Java version for building is 24, and maven-enforcer > > enforces it. Anything lower and the Java24+-only ML-KEM class > > JceKEM.java at > > sshd-common/src/main/java24/org/apache/sshd/common/util/security > > cannot be compiled. > > > > I don't require Java 25 because I don't want to force people to update > > to Java 25 if they already are using Java 24. Since it's a _minimum_ > > requirement, it's OK if it is a non-LTS version. After all, a higher > > LTS version exists. > > > >> Ayway, Java 25 installed locally. > >> > >> I have more issue with the Maven 3.9.11 requirement. > >> > >> This is making release testers a hard time. I had to spend 30 minutes > >> to reinstall all my env to get the build running. As much I can see > >> why Java in its latest version is needed, I seriously doubt an older > >> version of Maven is a blocker... > > > > From > > https://che01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmave > > n.apache.org%2Fdocs%2F3.9.10%2Frelease-notes.html&data=05%7C02%7Cchris > > toph.john%40macd.com%7Ca12eaa9fb15f4a508cec08de111f7d03%7Cfb673ffa32b2 > > 4d71b08c8c56f99c56ca%7C0%7C0%7C638967024108706124%7CUnknown%7CTWFpbGZs > > b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIj > > oiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2Bu1Xr5a6UntriLUXL%2FMi > > apA26m5pOvhVDhSkR1TRQSs%3D&reserved=0 > > > > "When running a build using Java 24 with an earlier version of > > Maven, > > there were a lot of errors and warnings, because many dependencies > > were not compatible with a Java 24 runtime. > > > > In Maven 3.9.10 those got updated, resulting in Maven 3.9.10 now > > has > > a far better support if you want to run your builds on Java 24." > > > > From > > https://che01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmave > > n.apache.org%2Fdocs%2F3.9.11%2Frelease-notes.html&data=05%7C02%7Cchris > > toph.john%40macd.com%7Ca12eaa9fb15f4a508cec08de111f7d03%7Cfb673ffa32b2 > > 4d71b08c8c56f99c56ca%7C0%7C0%7C638967024108726762%7CUnknown%7CTWFpbGZs > > b3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIj > > oiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=OcUtAz7dn0CdxoV2FBfNiHIG > > jxU4ARGQsVuqQQ4wkKI%3D&reserved=0 > > > > "Regression fixes and other improvements from Maven 3.9.10. All > > users > > already on Maven 3.9.x are advised to upgrade." > > > > So, yes, maven 3.9.11 _is_ required. > > > > Don't know how you are set up, but for me switching maven versions is > > very simple. My $PATH contains ~/bin/mvn/latest/bin, and > > ~/bin/mvn/latest is a symlink. I just download a new maven version, > > check the download, unpack to some directory, and then point that > > symlink to that directory. > > > > That's all. Henceforth all my shells, already open or new, use the new > > maven version. > > > > Cheers, > > > > Thomas > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For additional > > commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
