Bug 175174 [ErrorHandling] Back out of ILogDialog
We have determined that plugging an alternate dialog into the JFace layer will not cover our status handling requirements without breaking look and feel. It is possible to create an ErrorDialog using both the static method and the constructor. Moreover the ErrorDialog is subclassed frequently (10 times in the SDK currently) so using an alternate dialog breaks consistency. Our API request is to delete the experimental ILogDialog method and it's references.
bundles/org.eclipse.jface/src/org/eclipse/jface/dialogs/ErrorDialog.java
* Show the details portion of the dialog if it is not already visible.
     * This method will only work when it is invoked after the control of the dialog
     * has been set. In other words, after the <code>createContents</code> method
     * has been invoked and has returned the control for the content area of the dialog.
     * Invoking the method before the content area has been set or after the dialog has been
     * disposed will have no effect.
     * @since 3.1
     */
    protected final void showDetailsArea() {
        if (!listCreated) {
            Control control = getContents();
            if (control != null && ! control.isDisposed()) {
				toggleDetailsArea();
			}
        }
    }
    
    /**
     * Return whether the Details button should be included.
     * This method is invoked once when the dialog is built.
     * By default, the Details button is only included if
     * the status used when creating the dialog was a multi-status
     * or if the status contains an exception.
     * Subclasses may override.
     * @return whether the Details button should be included
     * @since 3.1
     */
    protected boolean shouldShowDetailsButton() {
        return status.isMultiStatus() || status.getException() != null;
    }