gnodet commented on pull request #400: URL: https://github.com/apache/maven/pull/400#issuecomment-756658988
> Guess the question is do we switch to junit4 ot junit5 directly today. I think in both cases we need to write the BaseTest as an extension (junit5) or rule (junit4) so the effort seems kind of the same to move to junit5 to me at the moment. Did you evaluate junit5 directly? Is there any issue? You're right. When rewriting the base class, it would be a good time to jump to unit 5. I did upgrade Camel to junit 5. Most of it is painless (though the arguments order of the assertions has been changed, so you need some regex skill...), but the pain comes when using specific unit 4 rules. I'm currently working on another PR to move the 3 duplicated `PlexusTestCase` classes to a new `maven-test-support` module so that they can be shared. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
