Bug 20633 inner "new interface" in a class - why option "static"? [code manipulation]
When you add an inner interface to a class or interface, the "new interface" dialog offers a checkbox "static". Wether an inner interface is static or not does not make a bit of a difference. So the main effect that checkbox is likely to have is, it confuses Java-newcomers. "Could you please tell me what this decision I have to make means?" (Nothing.) Get rid of that checkbox.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.java
}
		} catch (CoreException e) {
			JavaPlugin.log(e);
		}
		return null;
	}
	
	/**
	 * @deprecated Use getTypeComment(ICompilationUnit, String)
	 */
	protected String getTypeComment(ICompilationUnit parentCU) {
		if (PreferenceConstants.getPreferenceStore().getBoolean(PreferenceConstants.CODEGEN_ADD_COMMENTS)) {
			return getTypeComment(parentCU, String.valueOf('\n'));
		}
		return null;
	}
	/**
	 * @deprecated Use getTemplate(String,ICompilationUnit,int)
	 */
	protected String getTemplate(String name, ICompilationUnit parentCU) {
		return getTemplate(name, parentCU, 0);
	}
		
	
	/**
	 * Returns the string resulting from evaluation the given template in
	 * the context of the given compilation unit. This accesses the normal
	 * template page, not the code templates. To use code templates use
	 * <code>constructCUContent</code> to construct a compilation unit stub or
	 * getTypeComment for the comment of the type.