- All Known Implementing Classes:
@Deprecated public interface IFileModificationValidator
clients should subclass
FileModificationValidatorinstead of implementing this interface
The file modification validator is a Team-related hook for pre-checking operations that modify the contents of files.
This interface is used only in conjunction with the "org.eclipse.core.resources.fileModificationValidator" extension point. It is intended to be implemented only by the Eclipse Platform Team plug-in.
validateEditDeprecated.Validates that the given files can be modified. The files must all exist in the workspace. The optional context object may be supplied if UI-based validation is required. If the context is
null, the validator must attempt to perform the validation in a headless manner. The returned status is
IStatus.OKif this validator believes the given file can be modified. Other return statuses indicate the reason why the individual files cannot be modified.
files- the files that are to be modified; these files must all exist in the workspace
org.eclipse.swt.widgets.Shellthat is to be used to parent any dialogs with the user, or
nullif there is no UI context (declared as an
Objectto avoid any direct references on the SWT component)
- a status object that is OK if things are fine, otherwise a status describing reasons why modifying the given files is not reasonable
- See Also:
validateSaveDeprecated.Validates that the given file can be saved. This method is called from
IFile#appendContentsbefore any attempt to write data to disk. The returned status is
IStatus.OKif this validator believes the given file can be successfully saved. In all other cases the return value is a non-OK status. Note that a return value of
IStatus.OKdoes not guarantee that the save will succeed.
file- the file that is to be modified; this file must exist in the workspace
- a status indicating whether or not it is reasonable to try writing to the given file;
IStatus.OKindicates a save should be attempted.
- See Also: