Bug 17229 Java prefs - build preferences should be merged back with compiler ones
Build 20020521 Unless people understand our implementation, it is counter-intuitive for them to look under the 'builder' section for concerns which are still roughly compiler related... Here are some options (from Erich): 1) make builder a subnode of compiler - easy to do - not consistent with existing tab approach 2) squeeze it onto the first tab and rename it - dialog might get higher - need another title 3) add another tab "Building" (need a better name) - we would have the space to do so
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/CompilerPreferencePage.java
WorkbenchHelp.setHelp(getControl(), IJavaHelpContextIds.COMPILER_PREFERENCE_PAGE);
	}	
	/**
	 * @see PreferencePage#createContents(Composite)
	 */
	protected Control createContents(Composite parent) {
		TabFolder folder= new TabFolder(parent, SWT.NONE);
		folder.setLayout(new TabFolderLayout());	
		folder.setLayoutData(new GridData(GridData.FILL_BOTH));
		
		Composite warningsComposite= createWarningsTabContent(folder);
		Composite codeGenComposite= createCodeGenTabContent(folder);
		Composite complianceComposite= createComplianceTabContent(folder);
		TabItem item= new TabItem(folder, SWT.NONE);
		item.setText(JavaUIMessages.getString("CompilerPreferencePage.warnings.tabtitle")); 
		item.setControl(warningsComposite);
	
		item= new TabItem(folder, SWT.NONE);
		item.setText(JavaUIMessages.getString("CompilerPreferencePage.generation.tabtitle")); 
		item.setControl(codeGenComposite);
		item= new TabItem(folder, SWT.NONE);
		item.setText(JavaUIMessages.getString("CompilerPreferencePage.compliance.tabtitle")); 
		item.setControl(complianceComposite);
		
		validateSettings(null, null);
	
		return folder;
	}
	private Composite createWarningsTabContent(Composite folder) {
		String[] errorWarningIgnore= new String[] { ERROR, WARNING, IGNORE };