Bug 20666 Export JavaDoc should examine jdk compliance
The Export Javadoc wizard should examine the jdk1.3/jdk1.4 compliance for a project and add the appropriate javadoc switch by default to the javadoc args viewer. Result of not fixing: Javadoc users will get errors in the console complaining about all their assert statements, and then have to figure out the switches to add to correct this problem.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocWriter.java
private IPath fBasePath;
	/**
	 * Create a JavadocWriter on the given output stream.
	 * It is the client's responsibility to close the output stream.
	 * @param basePath The base path to which all path will be made relative (if
	 * possible). If <code>null</code>, paths are not made relative.
	 */
	public JavadocWriter(OutputStream outputStream, IPath basePath, IJavaProject project) {
		Assert.isNotNull(outputStream);
		fOutputStream= new BufferedOutputStream(outputStream);
		fBasePath= basePath;
		fJavaProject= project;
	}
	public void writeXML(JavadocOptionsManager store) throws IOException, CoreException {
		DocumentBuilder docBuilder= null;
		DocumentBuilderFactory factory= DocumentBuilderFactory.newInstance();
		factory.setValidating(false);
		try {
			docBuilder= factory.newDocumentBuilder();
		} catch (ParserConfigurationException ex) {
			throw new IOException();
		}
		Document document= docBuilder.newDocument();
		
		Element project= document.createElement("project"); 
		document.appendChild(project);
		project.setAttribute("name", fJavaProject.getElementName()); 
		project.setAttribute("default", "javadoc"); 
		Element javadocTarget= document.createElement("target"); 
		project.appendChild(javadocTarget);