You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The @Generated annotation is handy to quickly spot generated classes.
In addition, some tools like Google Error Prone, rely on it to distinguish between the regular and generated code. The missing annotation makes Error Prone practically unusable since hundreds of errors are reported for the code generated by jsonschema2pojo.
The text was updated successfully, but these errors were encountered:
You might be interested in this solution: #835 (comment). You can remove the paths that contain generated output from Error Prone's scanning.
We originally removed @Generated because it caused hassle for Android users: #577. Their classes would not compile without adding an additional library and it caused a lot of questions.
I do agree though, it's a lot nicer to annotate these generated classes correctly because a lot of tools will read that annotation.
We still support Java 8 though so I think we need to add javax.annotation.Generated or javax.annotation.processing.Generated depending on what we find is available.
The @Generated annotation is handy to quickly spot generated classes.
In addition, some tools like Google Error Prone, rely on it to distinguish between the regular and generated code. The missing annotation makes Error Prone practically unusable since hundreds of errors are reported for the code generated by jsonschema2pojo.
The text was updated successfully, but these errors were encountered: