Stephan Schroevers

@andreassiegel does running the toolchain setup with `-X -Dmaven.compiler.verbose=true` provide any further details? I'm asking because coincidentally I just started playing with such a setup, and I noticed that it...

^ This newline issue isn't specific to a Toolchain setup; it can also be reproduced without if one enables forking (`-D-Dmaven.compiler.fork=true`). I notice that in that case even `-X -Dmaven.compiler.verbose=true`...

Very nice that you figured it out @andreassiegel! For the more general issue that compiler failures sometimes happen without clear output, codehaus-plexus/plexus-compiler#66 may be an issue to keep an eye...

> Pretty soon we'll be able to leverage the Picnic recipes again That time has arrived :tada:.

#486 - Allow checks with the "suggestion" severity to be raised to "warning".

(Separate comment, to allow voting on the one above.) Thanks for opening this discussion! You asked for Github links; our code is closed source but I can share our config...

@codylerum you can have the compiler fail on warnings by passing `-Werror`. This is a standard `javac` flag, and it also works with warnings emitted by Error Prone.

Interesting topic. I've seen issues with `String.format` and the default locale several times in production code, most recently today. I think it's a problem worthy of Guava's help. As you...

In case you plan to lexicographically order all annotations: [this Error Prone code](https://github.com/PicnicSupermarket/error-prone-support/blob/28cf295606f8e4a58e3bee0f0bafacd80b916909/error-prone-contrib/src/main/java/tech/picnic/errorprone/bugpatterns/LexicographicalAnnotationListing.java) can serve as inspiration. Note that it sorts declaration annotations before type annotations; see also PicnicSupermarket/error-prone-support#182.

I updated #4586 with a multi-release JAR setup that seems to work, at least locally. TBD what aspect (if any) of the GitHub Actions configuration has to be adjusted.