olamy commented on PR #3179:
URL: https://github.com/apache/maven-surefire/pull/3179#issuecomment-3817046840
@juherr please note version 3.6.x (at least first alphas/betas/Mx whatever
name we use) will be anything but only multi providers simplification (no new
features at least for few version)
So either you upgrade to this version or you simply keep using the previous
version 3.5.x.
Not sure to understand what sort of `more incremental approach` could be
used?
regarding
> For example, would it be possible to keep the JUnit 5 provider enabled by
default while disabling legacy providers, but still allow running both side by
side during a transition phase?
you will be able to eventually do something such
```
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.6.xxx</version>
<dependencies>
<dependency>
<groupId>org.apache.maven.surefire</groupId>
<artifactId>surefire-junit3</artifactId>
<version>3.5.4</version>
</dependency>
</dependencies>
</plugin>
```
There will be some backward compatibility for the providers but maybe not
for long.
But what would be the benefit for someone doing such configuration? (again
if any issue just change back surefire plugin version)
If there is any issue with the testng-engine, I'm pretty sure the team there
will be happy to fix and release any issue quickly.
--
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]
