[GROOVY-11191] Control/alias properties for collected annotations

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.0.13
• Component/s: Compiler
• Assignee: Unassigned
• Reporter: Christopher Smith
• Created: 13/Oct/23 19:39
• Updated: 13/Oct/23 19:39

Description

@AnnotationCollector automatically and inflexibly maps properties on the collection annotation onto the collected annotations. This is particularly inconvenient when multiple annotations declare a property value():

@JsonTypeName // String value()
@CompileStatic // TypeCheckingMode value()
@AnnotationCollector
@interface StaticBody {}

Currently, the only way to support such behavior is to subclass AnnotationCollectorTransform and hand-write it (and I'm not even sure how, since the logic is not simple). It would be immensely helpful to be able to declaratively alias or even suppress mapping certain properties onto certain collected annotations (e.g., it would solve my use case to be able to skip applying value() to CompileStatic above).