jira-importer commented on issue #585: URL: https://github.com/apache/maven-invoker-plugin/issues/585#issuecomment-2957803846
**[Mikkel Kjeldsen](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER303566)** commented > So this output shows a lot of problems: > > * You failed to provide the conditions: Maven version, Java version, plugin versions > * The test requires Java 11, what for? Is that a JAva version specific issue? > * The IT passes with Maven 3.8.x, but fails with 3.9.x. > * Important plugins haven't been pinned The behavior in Maven 3.8.x is interesting because it suggests a different error in the test execution: it claims to run the test yet reports 0 tests run, which could well explain the missing output. I can see the class being compiled but I am unable to glean from the output of `-Dinvoker.debug` whether it confirms that hypothesis. In any case, I suspect this is just an artifact of using JUnit 5. Maven 3.6.3 and up combined with [m-surefire-p 2.22.0](https://blogsarchive.apache.org/maven/entry/apache-maven-surefire-plugin-2) and up behave as expected, while m-surefire-p 2.21.0 in the same versions of Maven fail to produce the expected output and Maven 3.8.8 apparently defaults to m-surefire-p 2.12.4. Perhaps because of SUREFIRE-1330. Besides this, under the reasonable assumption that no exceptional branching for these component versions occurs, the versions of * Java * Maven * Surefire have no bearing on the behavior of m-invoker-p's callstacks, which ultimately and independently end up producing insufficiently sanitized output. The question is only whether to... 1. ignore the issue 2. fix the issue locally inside m-invoker-p 3. punt the issue upstream to the writer -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
