Bug 88838 [Undo] - API cleanup - remove IContextConsultingOperationApprover
Early on this was involved in scenarios where editors examined other operations. This is no longer used. Operation approvers generally apply to all contexts and are installed at the OperationHistory level. Until there is a concrete need for this API it should be removed. It is gratuitous at this point.
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/operations/DefaultOperationHistory.java
}
		}
		return status;
	}
	/*
	 * (non-Javadoc)
	 * 
	 * @see org.eclipse.core.commands.operations.IOperationHistory#execute(org.eclipse.core.commands.operations.IUndoableOperation, org.eclipse.core.runtime.IProgressMonitor, org.eclipse.core.runtime.IAdaptable)
	 */
	public IStatus execute(IUndoableOperation operation, IProgressMonitor monitor, IAdaptable info) throws ExecutionException {
		Assert.isNotNull(operation);
		
		
		if (!operation.canExecute()) {
			return OPERATION_INVALID_STATUS;
		}
		
		/*
		 * If we are in the middle of an open batch, then we will add this operation's contexts
		 * to the open operation rather than add the operation to the history.  We will still
		 * execute it, but will dispose of it afterward.  Operations triggered during an operation
		 * are assumed to be model-related and we assume the undo of this related operation will be
		 * triggered automatically by the undo of the batching operation.
		 */
		boolean merging = false;
		if (batchingOperation != null) {
			
			if (batchingOperation == operation) {
				return OPERATION_INVALID_STATUS;
			}