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
* </p>
	 */	
	public JavaCapabilityConfigurationPage() {
		super(PAGE_NAME);
		fJavaProject= null;
		
		setTitle(NewWizardMessages.getString("JavaCapabilityConfigurationPage.title")); 
		setDescription(NewWizardMessages.getString("JavaCapabilityConfigurationPage.description")); 
		
		IStatusChangeListener listener= new IStatusChangeListener() {
			public void statusChanged(IStatus status) {
				updateStatus(status);
			}
		};
		fBuildPathsBlock= new BuildPathsBlock(ResourcesPlugin.getWorkspace().getRoot(), listener, true);
	}
	
	/**
	 * Initializes the page with the project and default classpaths.
	 * <p>
	 * The default classpath entries must correspond the the given project.
	 * </p>
	 * <p>
	 * The caller of this method is responsible for creating the underlying project. The page will create the output folder
	 * and source and library folders if required.
	 * </p>
	 * <p>
	 * The project does not have to exist at the time of initialization, but must exist when executing the runnable
	 * obtained by <code>getRunnable()</code>.
	 * </p>