olamy commented on PR #3191: URL: https://github.com/apache/maven-surefire/pull/3191#issuecomment-3395370068
> > > This is not OK. Such a cleanup can only happen in the next major IMHO. > > > > > > Why not? Version will be bumped from 3.5.x to 3.6.0 4.x is usually for plugin based on Maven core 4.x > > I fail to see the need to remove it unless it is broken which it is not This has been explained on mailing list I can re-explain a bit here, but I don't want to restart another thread in another location. See the threads here: - https://lists.apache.org/thread/wcs484ofy868ldnon8wwgr118zvthzsv - https://github.com/apache/maven-surefire/issues/3185#issuecomment-3383759077 There is a major refactoring to simplify the code. This mean upgrading junit platform to use this only for running test and simplify A LOT the current code. This uprade means junit3 not supported (which is the case as junit3 is not supported anymore). Again as I already said if you are stuck which such old version of junit3 which is not supported anymore you can configure pluginManagement to using last version of surefire supporting junit3. Or if someone really need a bugfix for junit3 support a bug fix branch can be made as well But the current code has a lot of technical debt, so nobody really wants to contribute (perfect writing here https://lists.apache.org/thread/3szgfk0v1ws8c7dwh26y8tcl0p7wmk9p0 Onward!! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
