| Summary: | Specify scope of an annotation | ||
|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Marc FLAUW <marc.flauw> |
| Component: | Annotations | Assignee: | Project Inbox <tigerstripe.annotations-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | etalelover, nmehrega |
| Version: | unspecified | ||
| Target Milestone: | 0.5M0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Marc FLAUW
Hi, Please note that TMF Shared Interface Infrastructure team has recently decided the team will not use the Annotation Framework in next release of tooling, that is, the team will keep using stereotypes. Now the issue can have low priority from the view of the team. best regards, Jinzhai It already is possible to specify annotation scope via the 'target' element of a 'definition' for org.eclipse.tigerstripe.annotation.core.annotationType extension point. Please see this documentation for more details: http://wiki.eclipse.org/Define_Tigerstripe_Annotations Specifically see excerpt: "Note that we have defined specific target types for these 2 annotations ('IModelComponent'), which means only Tigerstripe Model Components will be "annotable" with these 2 Annotation Types. " Examples are also available in Tigerstripe CVS (see org.eclipse.tigerstripe.annotation.example.person). |