Adam Gent

I'm just not sure the authors of JUnit share the same thoughts as JUnit is designed to crash in a specific context and it is their library to annotate ideally....

Perhaps an example of how this came up might shift the mindset. I have a method called `@Nullable Object findOrNull(input);`. With out assertNotNull being nullable I would have to do:...

https://github.com/TechEmpower/FrameworkBenchmarks/blob/master/frameworks/Java/officefloor/src/woof_benchmark_woof/src/main/java/net/officefloor/benchmark/FortunesSendResponse.java

@smillst happy to try to setup a small reproducible project if that helps?

@smillst Here is the reproducible project: https://github.com/agentgt/checker-issues It seems there is an issue with things enclosed in a `sealed` interface (even if they are not part of the hierarchy) where...

FWIW @smillst I have encountered a similar error that I can file a new bug if you like and or maybe there is a way to annotate the "sneak throw"...

Yeah its broken (maven + eclipse integration) or at least a good portion of it. It worked at one point and was great however I was using the workspace location...

Oh I forgot to say since you got the plugin to load (it doesn't even load for me these days) is that `m2e.jdt.annotationpath` should be workspace location. That is it...

@stechio > JRE (project-level "Java Build Path/Libraries" dialog): FAILURE (path saved (plugin works), but nullness analysis doesn't work!) I vaguely remember upgrading recently and null analysis being very broken so...

@SentryMan @rbygrave @Mechite For me the challenge in config is not so much formats (parsing) but where the key values are coming from and if they have to be transformed....