Bug 20674 JavaCapabilityConfigurationPage.init is not clearing the default path when classpath already exists
F4 JavaCapabilityConfigurationPage.init: The doc states that when defaultsOverrideExistingClasspath is set to false and a .classpath file already exists the setting from the classpath file is taken. code is defaultOutputLocation= null; defaultOutputLocation= null; is meant to be defaultOutputLocation= null; defaultEntries= null; Class is API and this bug would prevent cliants from using the functionality. No dependences so far, fix is riskless.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/JavaCapabilityConfigurationPage.java
}
	/**
	 * Returns the currently configured class path. Note that the class path might not be valid.
	 */	
	public IClasspathEntry[] getRawClassPath() {
		return fBuildPathsBlock.getRawClassPath();
	}
	
	/**
	 * Returns the Java project that was passed in <code>init</code> or <code>null</code> if the page has not
	 * been initialized yet.
	 */	
	public IJavaProject getJavaProject() {
		return fJavaProject;
	}	
	
	/**
	 * Returns the runnable that will create the Java project or <code>null</code> if the page has not been initialized.
	 * The runnable sets the project's classpath and output location to the values configured in the page and
	 * adds the Java nature if not yet set. It assumes that the project is created and opened.
	 *
	 * @return the runnable
	 */		
	public IRunnableWithProgress getRunnable() {
		if (getJavaProject() != null) {
			return new IRunnableWithProgress() {
				public void run(IProgressMonitor monitor) throws InvocationTargetException, InterruptedException {
					try {
						configureJavaProject(monitor);
					} catch (CoreException e) {