Pankraz76

Just kindly asking if this is something to be merged. I would like to volunteer on these kinds of trivial issues and help guide them through. Is there any way,...

Having not fully understood the issue, I’m wondering if it’s related to normalizing the directories as well. I’m also assuming this approach would only handle one level of directories. If...

when can we apply UpgradeToJava21? Do we need v17 support for longer time? gradle using checkstyle and they still on 8 so its quite a large range.

discovering the specialties took more than 2h to collect. Of course junit worth every effort. BUILD SUCCESSFUL in 3m 19s making this fully reprod. is first premise:

should have done more early related topics into one PR with dedicated commits... sorry for this inconvenience.

Kindly asking, if this is any good? @sbrannen @marcphilipp Assuming the junit rules could help to embrace some junit conventions and best practices. Thanks to the community.

yes of course. Its actually ment to be used as into. The dedicated junit rules make a lot of changes, meaning junit it not quite aligned with its own best...

this the classic one i´ve been doing wrong for 15 years, so seems junit too, which is nothing to be worried about its something everybody having issues with, everyone except...

8gb: ``` 2025-12-08T14:02:48.9702295Z ##[error]Exception in thread "RMI TCP Connection(idle)" java.lang.OutOfMemoryError: Java heap space ``` ``` 2025-12-08T12:48:20.2470402Z Unable to resolve classpath for sourceSet :wrapper-shared:testFixtures 2025-12-08T12:48:20.2471282Z org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$IllegalResolutionException: Resolution of the configuration ':wrapper-shared:testFixturesRuntimeClasspath'...

One could argue for moving the checkstyle verification to CI, considering the 5x performance difference. By using Spotless as the primary fixup and automation layer for checkstyle, we could significantly...