Bugzilla – Full Text Bug Listing
| Summary: | [plan] Declared annotation for 'enhancement' of existing annotations | ||
|---|---|---|---|
| Product: | [Tools] AspectJ | Reporter: | Andrew Clement <aclement> |
| Component: | Compiler | Assignee: | aspectj inbox <aspectj-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | DEVELOPMENT | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
believe there is another related issue concerning declare precedence and multiple declare @s unsetting the target field which is currently set for something already released |
Sometimes the target of a 'declare @' already has the annotation. This results in an error about a clash. It might be nice to allow the declare to augment the annotation that is there. @SomeAnno class Foo { } aspect X { declare @type: Foo: @SomeAnno(value="filled in") } So the aspect enhances the existing annotation by filling in the specified value. We would have to think about what to do if: - 'value' already exists in the target anno - other values already exist in the target anno