Bug 84446 OperationHistory should protect itself better against runtime exceptions
Since clients of the history might rely on getting certain events even if a operation causes runtime exceptions (for example listeners) the history should protect itself better agains runtime exceptions. This envloves: - listeners causing runtime exceptions in the call back - Operation execution causing runtime exceptions. In this case listeners must be informed as well.
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/operations/DefaultOperationHistory.java
}
	/*
	 * (non-Javadoc)
	 * 
	 * @see org.eclipse.core.commands.operations.IOperationHistory#closeOperation(boolean, boolean)
	 */
	public void closeOperation(boolean operationOK, boolean addToHistory) {
		if (fBatchingOperation != null) {
			if (operationOK) {
				notifyDone(fBatchingOperation);
				if (addToHistory) add(fBatchingOperation);
			} else {
				notifyNotOK(fBatchingOperation);
			}
			fBatchingOperation = null;
		}
	}
	
	/*
	 * (non-Javadoc)
	 * 
	 * @see org.eclipse.core.commands.operations.IOperationHistory#operationChanged(org.eclipse.core.commands.operations.IUndoableOperation)
	 */
	public void operationChanged(IUndoableOperation operation) {
		if (fUndo.contains(operation) || fRedo.contains(operation)) {
			notifyChanged(operation);
		}
	}
}