[GROOVY-7422] @AnnotationCollector could provide more control over how annotations are added in the presence of existing explicit annotations

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.3
• Fix Version/s: 2.5.0-alpha-1
• Component/s: xforms
• Assignee: Paul King
• Reporter: Paul King
• Created: 12/May/15 12:22
• Updated: 02/May/17 02:03
• Resolved: 16/May/15 06:15

Description

When expanding a meta annotation alias into its annotation collection, it is sometimes useful to be able to control how annotations are added in particular in the presence of existing explicit annotations. This issue proposes adding an annotation parameter to @AnnotationCollection which lets the addition of collected annotations be controlled in more flexible ways. The following modes are proposed for @AC:

DUPLICATE: Annotations from the annotation collection will always be inserted. After all transforms have been run, it will be an error if multiple annotations (excluding those with SOURCE retention) exist.

PREFER_COLLECTOR: Annotations from the collector will be added and any existing annotations with the same name will be removed.

PREFER_EXPLICIT: Annotations from the collector will be ignored if any existing annotations with the same name are found.

PREFER_COLLECTOR_MERGED: Annotations from the collector will be added and any existing annotations with the same name will be removed but any new parameters found within existing annotations will be merged into the added annotation.

PREFER_EXPLICIT_MERGED: Annotations from the collector will be ignored if any existing annotations with the same name are found but any new parameters on the collector annotation will be added to existing annotations.