Pankraz76

> * literally 3000 lines of warnings in the build (!!!) `-XepDisableAllWarnings` might was the missing key and should be the cure of this madness. Idk whats the point, beside...

thanks for your diplomatic support in guiding/guarding the overall quality goals. > `-XepDisableAllWarnings` might was the missing key and should be the cure of this madness. This should fix the...

zero warnings as requested: - https://github.com/diffplug/spotless/pull/2766

> like a concurrency issue what about changing this plugin to sequentiell execution to avoid this. Its very fast anyways so is could be an tmp fix, not adding up...

nice plz include `@After` also this is kind of a general topic having to watch many actually all? junit annotations. There will be new stuff to come for sure. right...

Actually, in the Maven plugin, it's working as expected. Just passing `-XepPatchLocation:IN_PLACE` alone will apply everything possible without requiring additional configuration. However, this violates the specification since the parameter must...

kindly requesting any feedback on this, considering: - https://github.com/junit-team/junit-framework/pull/5193 it seems there is something for every project to gain upon, thus embracing the conventional principle.

Yes, of course, please excuse my shortcomings on this. I'm wondering if the Maven wrapper is something for this project to consider, like other Google projects and most of the...

> the picnic checks are still reporting warnings that should up in the build log? exact. They seem to sneak through. When removing picnic and the parameter i still see...

one way is to checkout the dedicated PR and enable picnic again to see. [b3090bd3c5dd941459eefdfc37a66d463ffcd17c](https://github.com/diffplug/spotless/pull/2754/commits)