This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 320068 - Use model information in annotations
Summary: Use model information in annotations
Status: CLOSED DUPLICATE of bug 359863
Alias: None
Product: Tigerstripe (Archived)
Classification: Technology
Component: Annotations (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement with 4 votes (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-16 02:11 EDT by Marc FLAUW CLA
Modified: 2012-03-01 16:04 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc FLAUW CLA 2010-07-16 02:11:23 EDT 
Build Identifier: 

Tigerstripe Annotation Framework should support the use of model information in the annotations. For instance, in a TIP model, for a given long duration operation, we hope to specify events which are defined in the model and can be emitted during the execution of the operation. A list of such events is supported to be the value of an annotation named ‘emittedEvents’.  So when defining this annotation, it would be good to be able to select the list of events currently defined in the model and its modules. 
Current Tigerstripe Annotation Framework does not support this requirement. The value range of an annotation is defined in an eclipse plug-in which has no any knowledge about a model. 

This is an important requirement for TIP

Reproducible: Always
Comment 1 Richard Craddock CLA 2010-08-09 13:36:34 EDT 
This needs to be tied into the refactor framework.

Also we need to consider the "level" of model elemnt that we go to eg :

Any Class
Any Attribute
Any Method

or, as sugested by Marc's text - any Event?
Comment 2 Justin CLA 2010-08-19 07:47:03 EDT 
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
Comment 3 Navid Mehregani CLA 2012-03-01 16:00:33 EST 

*** This bug has been marked as a duplicate of bug 359863 ***
Comment 4 Navid Mehregani CLA 2012-03-01 16:04:07 EST 
See http://wiki.eclipse.org/I42_Release_Notes for more details.