Matthias Bünger
Matthias Bünger
I give up, I'm too stupid to make the Junit annotation find the properties and even when I apply the module patching setting from Pioneer to Junit to open java.util...
Please do for all maven repositories 🙈
I've read the discussion on ML and this ticket. Another point I see, which might introduce a third option, are version ranges. For example `strict` could disallow them by default...
We are also facing this issue everytime a dependency (for example our own `org.acme:myproject-core`) is updated in POM a tons of repositories, not definied somewhere in our maven or nexus...
What is the purpose for this? Unittests? If yes, then there are already JUnit extensions for this :)
As in all other "follow Oracle javadoc guidelines" this is PR is not about fully following, but only some formatting. Same as in other PR there are a missing method/parameter...
> * Out of curiosity, I want to know whether `pom.yaml`, `pom.json`, `pom.conf`, `pom.hocon`, `pom.toml` used by https://github.com/maveniverse/mason will replace `pom.xml` as the default in Maven 4 or Maven 5?...
Why not complete < JUnit 5.0.0
@olamy Is this PR still needed for further tests or are you done?
> Errors: Error: JUnitPlatformEnginesIT.testJupiterEngineWithAssertionsFailEmptyStringParameters:362 » SurefireVerifier org.apache.maven.shared.verifier.VerificationException: Text not found in log: AssertionsFailEmptyStringParameterJupiterTest.doTest