Bug 127721 - validateEdit() called from refactor operation?
Summary: validateEdit() called from refactor operation?
Status: RESOLVED DUPLICATE of bug 127714
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.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: 2006-02-14 10:24 EST by TP CLA
Modified: 2006-02-14 16:23 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description TP CLA 2006-02-14 10:24:55 EST
I am a pessimistic team provider trying to determine if a validateEdit() is called as part of a refactoring process.

Here is the scenario:
1) validateEdit() gives me the list of files involved, where validateSave() gives only one file at a time - I want to check out all files together (increased performance).

2) Not all users are allowed to rename files, so the IMoveDeleteHook moveFile() might not be allowed.  In this case, I don't want to check out a bunch of files in validateEdit().


Solution:
There should be a way to determine if I am in a refactor operation from validateEdit().  A kluge in Eclipse 2.1 was to check the shellContext parameter of the validateEdit().  If it was null, then it was in a refactor process.  If it was non-null, then the validateSave() was called from an editor.
Comment 1 Michael Valenta CLA 2006-02-14 16:23:11 EST

*** This bug has been marked as a duplicate of 127714 ***