Bug 76649 New 'Inexact Argument for Varargs' compiler option
* COMPILER / Reporting Inexact Argument for Varargs Method/Constructor Invocation * When enabled, the compiler will issue an error or a warning whenever a varargs method/constructor is invoked with an inexact * argument (e.g. Class.getMethod(String name, Class ... args ) invoked with arguments ("foo", null)) * with inexact type match. * - option id: "org.eclipse.jdt.core.compiler.problem.inexactVarargsArgument" * - possible values: { "error", "warning", "ignore" } * - default: "warning" To be added to the 1.5 tag on the compiler
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/CompilerConfigurationBlock.java
status.setError(PreferencesMessages.getString("CompilerConfigurationBlock.cpl14trg15.error")); 
				return status;
			}			
		}
		if (VERSION_1_4.equals(source)) {
			if (VERSION_1_1.equals(target) || VERSION_1_2.equals(target) || VERSION_1_3.equals(target)) {
				status.setError(PreferencesMessages.getString("CompilerConfigurationBlock.src14tgt14.error")); 
				return status;
			}
		} else if (VERSION_1_5.equals(source)) {
			if (!VERSION_1_5.equals(target)) {
				status.setError(PreferencesMessages.getString("CompilerConfigurationBlock.src15tgt15.error")); 
				return status;
			}
		}
		return status;
	}
	
	private IStatus validateMaxNumberProblems() {
		String number= (String) fWorkingValues.get(PREF_PB_MAX_PER_UNIT);
		StatusInfo status= new StatusInfo();
		if (number.length() == 0) {
			status.setError(PreferencesMessages.getString("CompilerConfigurationBlock.empty_input")); 
		} else {
			try {
				int value= Integer.parseInt(number);
				if (value <= 0) {
					status.setError(PreferencesMessages.getFormattedString("CompilerConfigurationBlock.invalid_input", number)); 
				}
			} catch (NumberFormatException e) {