Errors in the manifest before Require Bundle header throws compilation errors related to missing required bundle

[alshamams]

Whenever there is an error in the manifest especially before the Require Bundle header, the compilation errors that arise because of a missing required bundle are clobbered with the manifest parsing error, and this leads to confusion to the user.

[gireeshpunathil]

eclipse.pde/ui/org.eclipse.pde.core/src/org/eclipse/pde/internal/core/builders/BundleErrorReporter.java

Lines 113 to 115 in e91bba5

	if (fHeaders == null || getErrorCount() > 0) {
	return;
	}

The reason as I understood is:

• if there is at least one error in the manifest, the above logic kicks-in and validation returns
• this means the budledescription is not built
• this poses serious issues to the Java compiler, as the Require-Bundle header is not resolved

thinking aloud - why should we abort the validation when there is an error? why can't we proceed to build the bundle description? Will there by any side effect if we remove the check?