Bug 57283 JavaDocExport: if destination path has spaces, the JavaDoc is generated into the incorrect (truncated) path or fails [javadoc]
Steps to reproduce (Eclipse3.0M8): Create a project with any name; Create some classes there; Execute Export->Javadoc. In the wizard, in the destination editbox, type any name that contains spaces. If the spaces are only in the last segment of the path (say, c:\tmp\my project), the javadoc is just generated in the incorrect (truncated) location (in this example, c:\tmp\my). If there are spaces before the last segment (e.g., c:\Documents and Settings\user\My Documents\my project), generation only produces 2 empty folders (in this example, C:\Documents and the destination that was typed) and fails to do anything else.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocOptionsManager.java
/*******************************************************************************
 * Copyright (c) 2000, 2004 IBM Corporation and others.
 * All rights reserved. This program and the accompanying materials 
 * are made available under the terms of the Common Public License v1.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/cpl-v10.html
 * 
 * Contributors:
 *     IBM Corporation - initial API and implementation
 *     Sebastian Davids <sdavids@gmx.de> bug 38692
 *******************************************************************************/
package org.eclipse.jdt.internal.ui.javadocexport;
import java.io.File;
import java.io.FileOutputStream;
import java.io.IOException;
import java.util.ArrayList;
import java.util.List;
import java.util.StringTokenizer;
import javax.xml.parsers.ParserConfigurationException;
import javax.xml.transform.TransformerException;
import org.eclipse.jdt.launching.ExecutionArguments;
import org.eclipse.jdt.launching.IVMInstall;
import org.eclipse.jdt.launching.IVMInstallType;
import org.eclipse.jdt.launching.JavaRuntime;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.xml.sax.SAXException;
import org.eclipse.core.resources.IContainer;
import org.eclipse.core.resources.IFile;