On 10/13/26 10:45, Neil C Smith wrote: > On Tue, 13 Oct 2026 at 08:42, Michael Bien <[email protected]> wrote: >> did anyone give it a try? > ... >> btw you might see warnings in the form of: > ... >> when switching from maven 3.10.x (or 4.x rc) to maven 3.9.x. > As you know from conversations elsewhere I've done a bit of testing. > I'm a little on the fence about whether we should merge. It would > certainly be nice to keep up-to-date. On the other hand, the lack of > engagement with this thread, we had that once before when we moved the security manager layer removal PR almost two releases waiting for more feedback. Would have been less work in retrospect to merge it right away given that we had to add more workarounds with extra flags everywhere etc ;)
> and the fact that it brings some major > changes that have not been given a lot of testing does ring some alarm > bells. > > People can opt in to use 3.10 for builds via mvnw, and we could make a > note of how on the release notes. Issues like the above warning, the > reported issue with platform builds, etc. show there is still some > things to consider. would be good to do in any case because this will occur in both scenarios. If someone runs mvn 3.10 or 4 at any point and it downloads something into the local repo, warnings will show up during the next time NB builds something if NB remains on 3.9. The interesting aspect about 3.10 is that it is compatible with 3.9 - 4.x. The warnings in this particular context should be harmless btw. I checked and 3.9 would simply download everything again while complaining a little bit. > I'm curious how many people will still be > building with 3.9 for a while anyway. could go quick. It looks like a regular update release from the outside. Depends on how many read release notes during dependabot merge and notice the resolver trojan horse ;) > If we do merge, we might want to emphasise some key things that need > testing with rc1. yep would be good so that we can revert early if something happens. But even if we revert after the second week we should be fine since nothing builds on top of it + NB 31 already shipped with 3.9.16 so it wouldn't require much additional testing. > Yes, not the most helpful thing to say, I know, but ... following your lead! > :-) currently leaning a little bit towards merge (probably Wednesday before freeze) assuming no issue shows up. And leave #9694 and followup refactorings for NB 33. -mbien > > Best wishes, > > Neil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
