Stephane, the problem is with Spring upgrade policy as I have understood.

What about releasing RC4 for you?
Do you really need to have SUREFIRE-1546 done? We do not want to enable it
implicitly as it is done in master right now, and therefore M4 needs to
take more time to enable this feature via configuration.

I see that the policy is against itself. If you concentrate only on
policies with project dependencies, you won't break anything.
We made a big investment (SUREFIRE-1614, ...) to not to break current
users. So please let us continue our work and let you and yourself use
3.0.0-M3 and continue whatever it means with Spring policies.Our plan is to
not to break backwards compatibility till 3.0.0-M5.

There is reason that you use Surefire in your project and provide us with
feedback. We can always release milestones or RCs (which don't have
different meaning for me).

Meanwhile, please check it out with version 3.0.0-M4-SNAPSHOT from
https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-surefire-plugin/
(plugin repository) and let us know with the feedback.

Is RC4 legal for your policies?

Cheers
Tibor


On Mon, Feb 25, 2019 at 8:54 AM Stephane Nicoll <stephane.nic...@gmail.com>
wrote:

> Hi everyone,
>
> It's great to see the progress on Surefire 3.0 and I wanted to reach out to
> discuss a practicable problem with the 2.x line. There are a number of
> fixes for JUnit 5 that are only available in the 3.x line that isn't GA
> yet. [1][2]
>
> Putting my Spring Boot hat for a min, this actually prevents us from
> upgrading our test support to JUnit 5: our plan is to offer maximum
> flexibility by providing the vintage engine (so that users can keep their
> tests and migrate at their own pace).
>
> We can't upgrade to a milestone as our upgrade policy prevents that
> (regardless of how stable this is and especially since backward
> incompatible changes have been pushed to the latest milestone). So we're
> kind of stuck.
>
> Would there be an appetite to backport those fixes and release a 2.22.2?
>
> Thanks,
> S.
>
> [1] https://issues.apache.org/jira/browse/SUREFIRE-1614
> [2] https://issues.apache.org/jira/projects/SUREFIRE/issues/SUREFIRE-1546
>

Reply via email to