Bug 271153 - Why is FileRevision#getFileRevisionFor(IFile) deprecated
Summary: Why is FileRevision#getFileRevisionFor(IFile) deprecated
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.4.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-03 13:02 EDT by Michael Valenta CLA
Modified: 2019-09-06 16:09 EDT (History)
1 user (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 Michael Valenta CLA 2009-04-03 13:02:19 EDT 
The method FileRevision#getFileRevisionFor(IFile) is marked as deprecated with the reason "This method doesn't do anything useful so it has been deprecated.". To me, this method is useful because I need to create an IFileRevision for a local file in order to provide logical model support and this is the only API available to do this. If there is some other way to do this now, the deprecation message should say this. Otherwise the method should not be deprecated.
Comment 1 Szymon Brandys CLA 2009-04-03 14:10:43 EDT 
(In reply to comment #0)
> Otherwise the method should not be deprecated.

Looking at the history of FileRevision, this method was marked as deprecated by Michael V. ;-) It was deprecated in 3.4 and nothing has change since then. 

We could make this quick fix, but let me first ask PMC. I have to double check if this change is not considered as API change.
Comment 2 Michael Valenta CLA 2009-04-03 14:32:11 EDT 
I'm not overly concerned about the change getting into 3.5 as long as the method doesn't disappear.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:39 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.