Bug 14421 Old .CLASS Files Are Not Deleted
When creating a project that does NOT use source folders (and does not use a bin directory for .class files) the .java and .class files are stored together in the Java package structure. When converting a project to use source folders (and the required bin directory for .class files), the old .class files stored in the Java package structure are NEVER DELETED by Eclipse. This is a bug for Eclipse 1.0 and 2.0. Since I use WSDD 4.0 (which is built on Eclipse 1.0), I've seen compilation errors due to the fact that the compiler/JDT is using old .class files rather than the new ones in the project's bin directory. I have not managed to reproduce the compile errors in build 20020416. But since the old .class files should have been deleted this is still a bug for the latest build.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPage.java
WorkbenchHelp.setHelp(control, IJavaHelpContextIds.NEW_JAVAPROJECT_WIZARD_PAGE);
	}
	
	/**
	 * Forces the initialization of the Java project page. Default classpath or buildpath
	 * will be used if set. The initialization should only be performed when the project
	 * changed or default paths have changed. Toggeling back and forward the
	 * pages without changes should not re-initialize the page, as changes
	 * from the user will be overwritten.
	 */
	protected void initBuildPaths() {
		fBuildPathsBlock.init(getNewJavaProject(), fOutputLocation, fClasspathEntries);
	} 
	/**
	 * Extend this method to set a user defined default class path or output location.
	 * <code>initBuildPaths</code> is called when the page becomes visible the first time
	 * or the project or the default paths have changed.
	 */	
	public void setVisible(boolean visible) {
		if (visible) {
			
			if (fProjectModified || isNewProjectHandle()) {
				
				initBuildPaths();
				fProjectModified= false;
			}
		}
		super.setVisible(visible);
	}