How to "Ignore optional compile problems" by default on generated code or any source folder whose content was generated ? #1941
Unanswered
VolatileLongPseudoRandom
asked this question in
Q&A
Replies: 1 comment
-
Just to add more : since I had an issue with toolchains not being "supported", I've simply "reconfigured" (Alt + F5) my project after ignoring Toolchains execution, disabling the "Clean project", and the Source Folder for which I had checked Ignore optional compile problems were all reconfigured, ... This is now produce 2064 warnings which may hiding other important warnings (like deprecation and so on). :( |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have remarked that whenever I use the following plug-ins or annotations processors, I have to frequently tick back the "Ignore optional compile problems" so that warnings in generated source code are ignored :
org.openapitools:openapi-generator-maven-plugin:7.9.0
org.openjdk.jmh:jmh-generator-annprocess:1.37.0
: I suppose this is configured in Eclipse using APT.I don't know why but I can assume the folder (and its configuration) was deleted in Eclipse and Eclipse sees it as "new".
Since the plug-in or annotations processor may never get the appropriate
@SuppressWarnings("all")
, is there a way to configure m2e to automatically tick Ignore optional compile problems in the Source Folder ?Beta Was this translation helpful? Give feedback.
All reactions