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
Generated code, by default, contains a javax.annotation.Generated (Java 8 and less) or javax.annotation.processing.Generated (Java 9+) annotation, which contains a bit of information about:
The fact that jOOQ generated the class
The jOOQ version that generated the class
The catalog and schema version if provided by relevant SPIs
The timestamp of code generation
While the catalog and schema versions can be useful to prevent re-generation of generated code when the underlying schema version has not changed (e.g. provided by Flyway), the code generation timestamp in particular is quite annoying when generated code is being checked in. It also prevents incremental compilation for no good reason, as file content will always have changed because of this timestamp, even if the rest of the file remains untouched.
The presence of schema version provider or catalog version provider configurations will continue to enforce the generated annotation, so user code will probably not break, unless users wrote their own annotation processing.
The text was updated successfully, but these errors were encountered:
Sorry to dig this out, just a quick question. I'm updating the jooq version and noticed that @generated was gone. That lead me to seeing its default is now "false".
From what I see here, the reason was the annoying timestamp and I had similar issues before using another code gen tool(dagger). However I don't see any timestamps currenty: @Generated( value = { "https://www.jooq.org", "jOOQ version:3.14.15" }, comments = "This class is generated by jOOQ" )
so I was wondering, am I missing something?
Generated code, by default, contains a
javax.annotation.Generated
(Java 8 and less) orjavax.annotation.processing.Generated
(Java 9+) annotation, which contains a bit of information about:While the catalog and schema versions can be useful to prevent re-generation of generated code when the underlying schema version has not changed (e.g. provided by Flyway), the code generation timestamp in particular is quite annoying when generated code is being checked in. It also prevents incremental compilation for no good reason, as file content will always have changed because of this timestamp, even if the rest of the file remains untouched.
The presence of schema version provider or catalog version provider configurations will continue to enforce the generated annotation, so user code will probably not break, unless users wrote their own annotation processing.
The text was updated successfully, but these errors were encountered: