Ignoring "Type not found" stub warnings

[Roded Bahat]

Hi,

Is it somehow possible to have CheckerFramework not output the following warnings when a type referenced in  stub is missing?

warning: /home/user/buildSrc/checkerframework/kr.pe.kwonnam.slf4jlambda.LambdaLogger.astub:(line 5,col 1): Type not found: kr.pe.kwonnam.slf4jlambda.LambdaLogger

Thanks

[Michael Ernst]

Yes, it is possible.  The first item in the "Troubleshooting stub libraries" section of the manual discusses the -AstubNoWarnIfNotFound command-line argument.  Could you try that?

-Mike

--

---
You received this message because you are subscribed to the Google Groups "Checker Framework discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to checker-framework-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/checker-framework-discuss/e152e21d-94ae-4147-9885-e0cd8cbbbbc3n%40googlegroups.com.

[Roded Bahat]

Thanks for the reply Mike.

I've tried that flag (-AstubNoWarnIfNotFound=true) using the latest checkerframework version and gradle plugin and the warnings persist.

[Michael Ernst]

That is odd.  I'm sorry to hear it.

Could you please open an issue with a full reproduction?  Then we will fix it.

Thanks,

-Mike

To view this discussion on the web visit https://groups.google.com/d/msgid/checker-framework-discuss/0010a7a2-e06b-4c2b-a142-c848d9dbbadcn%40googlegroups.com.

[Roded Bahat]

Hi Mike,

Yes:

https://github.com/typetools/checker-framework/issues/5390

Thanks a lot.

Roded