Stephan Schroevers

I started looking into this, and the topic is quite a rabbit hole, both in terms of regex matching behavior and invalidate test cases. I tried my best at cleaning...

But that would prevent one from using Immutables i.c.w. other annotation processors, no? A more appropriate solution seems to compile with `-Xlint:-processing` . See also e.g. https://github.com/spring-projects/spring-boot/issues/6421#issuecomment-273907960 and [JDK-6999068](https://bugs.openjdk.java.net/browse/JDK-6999068).

Great idea. In terms of "how to implement": likely [Error Prone](https://github.com/google/error-prone) is more suitable for such a check (with the added benefit that it can automatically emit appropriate fixes). NB:...

> I incline OpenRewrite might be slightly better at suggesting the fixes. Perhaps; as a long-time user of Error Prone and one of the primary devs behind [Error Prone Support](https://github.com/PicnicSupermarket/error-prone-support)...

This script currently draws from the [Pingdom IP whitelist](https://my.pingdom.com/probes/ipv4). Whitelisting AWS IPs wouldn't help for the primary use case. That said, I do see an AWS Lambda use case: users...

@razvanmuscalu the way this works on Github is that you fork this repository, push a new branch with your changes to that fork, and then open a PR against this...

Suggested commit message: ``` Introduce generic `run-integration-test.sh` script (#1141) This new script contains reusable logic extracted from `integration-tests/checkstyle.sh`, facilitating the introduction of additional integration tests. ```

The build now fails because Jitpack [again](jitpack/jitpack.io/issues/5741#issuecomment-2322956264) lost some artifacts. I'll try to prioritize #1314, as that would be the cleanest way to move forward.

I wonder whether we should default to a more permissible name pattern (e.g. `LOG(GER)?`), and then internally fix that to just `LOG`. This may ease external adoption. (Perhaps using CodeQL...

Cool. I'll open a PR once I have an initial prototype (which won't be until next weekend, I expect). My tentative plan of attack is as follows: 1. Manually annotate...