Sterling Greene
Sterling Greene
a part of #26365
`@Rule` are also affected by this.
@marcphilipp since we don't use `BlockJUnit4ClassRunner`, `@Rule`'s are also ignored.
@itkhanz is there something that's missing from the Gradle generated reports that are available in the TestNG version? I think we would prefer to just support the Gradle generated reports.
@bot-gradle test this
I believe the fix for https://github.com/gradle/gradle/issues/29024 also fixed this by defensively treating a non-working WindowsRegistry service as if there are no Windows registry provided JDKs.
No, we would still be able to search for JDKs through other methods.
I think the issue is that there's a circular evaluation order introduced by lines like this: ``` jvmArgs "-javaagent:${classpath.find { it.name.contains("jmockit") }.absolutePath}" ``` This causes the classpath of the Test...
Is this a new behavior (in 8.5?) or is there a version where this was known to work?
OK, I didn't think this was new behavior either. This isn't particular to `getAllJvmArgs`, but I can see how it's unexpected that just getting a list of strings could break...