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
* The source code of the new type will be formtted using the platform's formatter. Needed 
	 * imports are added by the wizard at the end of the type creation process using the given 
	 * import manager.
	 * </p>
	 * 
	 * @param newType the new type created via <code>createType</code>
	 * @param imports an import manager which can be used to add new imports
	 * @param monitor a progress monitor to report progress. Must not be <code>null</code>
	 * 
	 * @see #createType(IProgressMonitor)
	 */		
	protected void createTypeMembers(IType newType, ImportsManager imports, IProgressMonitor monitor) throws CoreException {	
		
		
		
		
		
	}	
	
		
	/**
	 * @deprecated Instead of file templates, the new type code template
	 * specifies the stub for a compilation unit.
	 */		
	protected String getFileComment(ICompilationUnit parentCU) {
		return null;
	}
	
	private boolean isValidComment(String template) {
		IScanner scanner= ToolFactory.createScanner(true, false, false, false);