Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 354920

Summary:	CompareRevisionAction does not make use of ModelProviders
Product:	[Eclipse Project] Platform	Reporter:	Laurent Goubet <laurent.goubet>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	remy.suen
Version:	4.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Laurent Goubet

2011-08-17 05:11:46 EDT

When we use the following actions that trigger the use of "OpenRevisionAction" :

Show the History view :
- Right-click a file : Team > Show History
- Right-click a file : Compare With > History...

Then select one of the following :
- Right-click a local version and select "Compare Current with Local"
- Right-click a remote version and select "Compare Current with <revision number>"
- Select two versions, right-click and select "Compare with Each Other"

Team ends up comparing a "Resource" to a "Revision" or two "Revision"s with each other without ever considering the ModelProvider or the ResourceMapping corresponding to the selected resource.

Comment 1 Remy Suen

2011-08-17 06:15:45 EDT

What SCM system is this? SVN?

Comment 2 Laurent Goubet

2011-08-17 06:41:50 EDT

Hi Rémy,

This was tested under both EGit and CVS. I raised this against the more generic "Team" since neither of those SCM seem to alter anything there.

The actual action that is called is org.eclipse.team.internal.ui.actions.CompareRevisionAction, not OpenRevisionAction :s.

Comment 3 Lars Vogel

2019-11-14 03:27:08 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.