Le jeu. 5 févr. 2026 à 12:59, Elliotte Rusty Harold <[email protected]> a écrit :
> On Thu, Feb 5, 2026 at 6:48 AM Romain Manni-Bucau <[email protected]> > wrote: > > > > > TestNG main consumer was EE suite due to the xml configuration, then most > > moved to arquillian and JUnit 4 and now they (+ their sibling > microprofile > > projects) moved to JUnit5 stack. > > Java EE was one consumer of TestNG, hardly the only one. Presto also > uses it with Maven, last I checked, and there are many others. > Migration is pretty trivial if you review it (speaking of presto but others are generally as simple) and once again it is not really the point since dropping testng support from surefire means we do support testng (no typo in the sentence). Point is more than there is no more demand for TestNG support. To rephrase it, for me questions are: 1. is testng alive -> yes but really maintenance mode in you review the commits == we must enable to run it somehow but at low cost if possible 2. does surefire need any code to support testng -> no, so why do we have it these days except legacy we can drop for maven 4? Side is: the fact surefire does add an abstraction on another abstraction now also literally blocks end users to use what surefire does abstract - as always, an abstraction is a good way to drop features users can want to use, since technically it can't be justified in our context I think we can drop it. > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
