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
public List getSuperInterfaces() {
		return fSuperInterfacesDialogField.getElements();
	}
	/**
	 * Sets the super interfaces.
	 * 
	 * @param interfacesNames a list of super interface. The method requires that
	 * the list's elements are of type <code>String</code>
	 * @param canBeModified if <code>true</code> the super interface field is
	 * editable; otherwise it is read-only.
	 */	
	public void setSuperInterfaces(List interfacesNames, boolean canBeModified) {
		fSuperInterfacesDialogField.setElements(interfacesNames);
		fSuperInterfacesDialogField.setEnabled(canBeModified);
	}
			
	/**
	 * Returns the resource handle that corresponds to the compilation unit to was or
	 * will be created or modified.
	 * @return A resource or null if the page contains illegal values.
	 * @since 3.0
	 */
	public IResource getModifiedResource() {
		IType enclosing= getEnclosingType();
		if (enclosing != null) {
			return enclosing.getResource();
		}
		IPackageFragment pack= getPackageFragment();
		if (pack != null) {
			return pack.getCompilationUnit(getTypeName() + ".java").getResource();