Bug 45460 [Workbench] Disable of autobuild on Workbench#init no longer needed
In the Workbench#init(String[] commandLineArgs, final Display display) method, the disable of the autobuild while editors are opened should no longer be needed since autobuilds are now done in the background. Actually, keeping the disable in is a problem because, on startup, the workbench blocks (busycursor) while the build is taking place, making the user wait needlessly.
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchAdvisor.java
workspace.setDescription(description);
			} catch (CoreException exception) { 
				MessageDialog.openError(
					null, 
					IDEWorkbenchMessages.getString("Workspace.problemsTitle"),	
					IDEWorkbenchMessages.getString("Restoring_Problem"));		
			}
		}
	}	
	/**
	 * Restore auto builds if temporarily disabled.
	 * Assumes that workbench windows have already been restored.
	 * <p>
	 * Use a WorkspaceModifyOperation to trigger an immediate build.
	 * See bug 6091.
	 * </p>
	 */
	private void enableAutoBuild() {
		if (autoBuild) {
			IWorkbenchWindow windows[] = PlatformUI.getWorkbench().getWorkbenchWindows();
			Shell shell = windows[windows.length - 1].getShell();				
			try {
				WorkspaceModifyOperation op = new WorkspaceModifyOperation() {
					protected void execute(IProgressMonitor monitor) throws CoreException {
						monitor.setTaskName(IDEWorkbenchMessages.getString("Workbench.autoBuild"));	
						IWorkspace workspace = ResourcesPlugin.getWorkspace();
						IWorkspaceDescription description = workspace.getDescription();
						description.setAutoBuilding(true);
						workspace.setDescription(description);
					}