That is the point. If not built in it has almost no value compared to groups since i doubt you ll write a plugin to a mvn plugin in your project - needs to be seriously generic for your business to do it IMO.
That said there are open doors for tests filtering for surefire without relying on the backing testing impl - ie aligning junit and testng with fancy features. Not adding it is not a blocker but would have been a nice feature to have. Le 18 juin 2015 19:49, "Tibor Digana" <[email protected]> a écrit : > I think it would not be difficult to dictate the SurefireProvider to use > specific JUnit runner or implement SurefireProvider by yourself and specify > then SPI class for it and list plugin dependency with the provider. > You can of course use Maven executions or just repeat the invoke(). > > We want to provide surefire extension API, but this is quite a lot of to do > in order to have such functionality generic and pluginable. > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/controlling-surefire-execution-just-with-a-set-of-runners-tp5837884p5837897.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
