Repository navigation
Use Jakarta's @Generated annotation if available #1602
Description
Activity
sourceversion > 8 is likely to be true in almost all compilations by this point, right? Especially for people that care about Jakarta.
Perhaps switch the conditions:
if in classpath: jakarta.annotation.Generated // new else if sourceVersion > 8: javax.annotation.processing.Generated else if in classpath: javax.annotation.Generatedsourceversion > 8 is likely to be true in almost all compilations by this point, right? Especially for people that care about Jakarta.
Unfortunately, that's not the case—which is why this whole thing came up. The Google Cloud libraries are still built with Java 8.
After
javax.annotation.Generatedwas deprecated in Java 9, AutoValue and other users ofGeneratedAnnotationsstarted using the newjavax.annotation.processing.Generatedreplacement if it was available (source version > 8), falling back to the deprecated one otherwise:However, it doesn't look for the new EE replacement, which was repackaged
jakarta.annotation.Generated. Some users want to switch to that annotation when compiling for Java 8.We could change
GeneratedAnnotationsto use the following logic:Alternatively, or in addition, we could add a supported option to each of our processors that lets users specify which
@Generatedannotation they want the processor to emit, which would let users override that default logic in case they want to emit a different one.[From a discussion with @suztomo.]