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/JavadocSpecificsWizardPage.java
}
		});
		fAntBrowseButton.addSelectionListener(new SelectionAdapter() {
			public void widgetSelected(SelectionEvent event) {
				String temp= fAntText.getText();
				IPath path= new Path(temp);
				String file= path.lastSegment();
				if (file == null)
					file= "javadoc.xml";
				path= path.removeLastSegments(1);
				temp= handleFolderBrowseButtonPressed(path.toOSString(), fAntText.getShell(), JavadocExportMessages.getString("JavadocSpecificsWizardPage.antscriptbrowsedialog.title"), JavadocExportMessages.getString("JavadocSpecificsWizardPage.antscriptbrowsedialog.label")); 
				path= new Path(temp);
				path= path.addTrailingSeparator().append(file);
				fAntText.setText(path.toOSString());
			}
		});
	} 
	private void doValidation(int VALIDATE) {
		File file= null;
		String ext= null;
		Path path= null;
		switch (VALIDATE) {
			case OVERVIEWSTATUS :
				fOverviewStatus= new StatusInfo();
				if (fOverViewButton.getSelection()) {
					path= new Path(fOverViewText.getText());
					file= path.toFile();
					ext= path.getFileExtension();
					if ((file == null) || !file.exists()) {
						fOverviewStatus.setError(JavadocExportMessages.getString("JavadocSpecificsWizardPage.overviewnotfound.error"));