Bug 127808 - [Actions] Team context menu should be available on editors for repository files
Summary: [Actions] Team context menu should be available on editors for repository files
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact: Szymon Brandys CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 196349
  Show dependency tree
 
Reported: 2006-02-14 12:55 EST by Markus Keller CLA
Modified: 2019-09-06 16:14 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2006-02-14 12:55:47 EST
I20060214-0010

The Team context menu should be available on editors for repository files to allow comparisons, show annotations, show in history, etc.
Comment 1 Michael Valenta CLA 2007-03-26 14:37:41 EDT
This should be doable with the new menu support. That is, I'm sure it is doable using objectContributions by associating the actions (Show Annotation, Compare With, Show History) with the editor input so there should be a way to do it with the new menu story as well.
Comment 2 Michael Valenta CLA 2007-04-17 10:13:07 EDT
For 3.3, we should just use object contributions for this. We should do a similar thing that we do for files but instead we should contribute to objects that adapt to CVSFileRevision (instead of IFile).
Comment 3 Michael Valenta CLA 2007-04-27 10:47:59 EDT
I've done a bit more investigation and it turns out that it is a bit more complicated when you are adapting to something other than IResource. Basically, we would need to create a CVS specific FileRevisionEditorInput so we could contribute the items to the input. Unfortunately, there are some places where we would require API in Team to do this. I would rather wait until 3.4 so we can get all the places then to have the menu appear sometimes. 
Comment 4 Michael Valenta CLA 2007-06-22 11:43:23 EDT
It doesn't make sense to mark a bug P5 if it is targeted for 3.4. I believe this bug is important since it will ensure that the required capabilities are available from the Workbench and Team.
Comment 5 Tomasz Zarna CLA 2008-04-17 06:57:02 EDT
Updating the target milestone to better match the reality.
Comment 6 Szymon Brandys CLA 2009-03-06 05:51:33 EST
During M7 I'll verify whether it's doable for 3.5.
Comment 7 Szymon Brandys CLA 2009-05-08 06:11:17 EDT
Removing 3.5 target milestone. We are in the end-game now. If anyone thinks this should be targeted at 3.6, please let me know.
Comment 8 Eclipse Webmaster CLA 2019-09-06 16:14:21 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.