Adam Gent

I'm with @bowbahdoe on this. JSpecify unlike Checkerframework and Eclipse null analysis does not really specify if checking is static only. That is it is not unreasonable for applications to...

I didn't have time to elaborate yesterday but JSpecify in terms of Maven should be ```xml org.jspecify jspecify 0.3.0 compile ``` And here is the controversial part if you are...

While you can get away with `implementation` and module-info.java `requires` (and `requires static`) I don't think it is a good idea. > Important for them is seeing the annotations on...

@cpovirk I'm wagering why @SentryMan and I see the module is because our stuff (we both write APT plugins) are running as an annotation processor and not a compiler plugin....

@cpovirk Can you try putting the plugin on the classpath and or regular `--processor-path` and then put the code on the module-path or classpath? Basically we have a nice 2x2...

FWIW @cpovirk you seem more effective than Chat GPT or at least the free version 😄 Thanks for doing that! I will have to figure out someway to make it...

It just occurred to me that I don't actually check if it is a named module. I just check to see if an annotation is on the module and it...

> Maybe what you're seeing with JStachio is that you can pick up annotations from the module you're compiling even if your dependencies are in the unnamed module? That much...

I think where @SentryMan and myself got confused is the tool in this case the annotation processor does not need to run on the module-path but the code being analyzed...

@cpovirk I don't blame you. I was relooking at my old comments regarding this that I completely forgot as well 😆 . Damn modules be complicated.