why not JUnit 5?

The rest of the code base is junit 4 and want to have a minimal change. But of course Junit 5 would be better. Let me take a look on it tomorrow. Thanks for your feedback.

@slawekjaranowski

Many tests are based on PlexusTestCase and that needs JUnit 3. Therefore, I only eliminate the direct dependency on JUnit 3 in this PR. I will put it on my to-do list.

Do you have a hint how to handle PlexusTestCase with JUnit 5?

@slawekjaranowski

Many tests are based on PlexusTestCase and that needs JUnit 3. Therefore, I only eliminate the direct dependency on JUnit 3 in this PR. I will put it on my to-do list.

Do you have a hint how to handle PlexusTestCase with JUnit 5?

We can try with plexus-testing - example:
https://github.com/codehaus-plexus/plexus-testing/blob/master/src/test/java/org/codehaus/plexus/testing/PlexusTestJavaxTest.java

@slawekjaranowski Thx for the link, I will take a look on it.

also new version released with simple documentation
https://codehaus-plexus.github.io/plexus-testing/

@slawekjaranowski

migrate one test based on your hint. Unfortunately, I have to use PlexusExtension directly, because of some container configuration customize. Do you think this is the way to go? Or did I oversee anything?

@slawekjaranowski

Migrate it completely to PlexusTest and junit 5. In some cases we need a junit dep because of modello compiler tests.