How do I remove javascript validation from my eclipse project?

In-depth guide: Deeper into the weeds

To have better control over JavaScript validation, let's dive into more advanced settings and walk through alternate workarounds.

Using wildcard exclusions and adjusting builder settings

To exclude specific files using a wildcard pattern:

1. Go to Project Properties -> JavaScript > Include Path.
2. Use the Wildcard pattern or Browse option to select files or folders you wish to exclude.

To disable the JavaScript Validator in your builder settings:

1. Go to Project Properties -> Builders.
2. Uncheck JavaScript Validator.

After you make any changes, give Eclipse a restart to ensure the new settings are in full swing.

Negotiating JQuery errors

If you regularly encounter pesky JQuery errors, consider renaming problematic .js files as a last resort, or editing the buildCommand in your .project file:

<buildCommand>
    <!-- Why JavaScript Validator always gets invited to parties? -->
    <!-- Because it validates everything! 😂 -->
    <name>org.eclipse.wst.jsdt.core.javascriptValidator</name>
    <arguments>
    </arguments>
</buildCommand>


Removing or commenting out these lines will ban JavaScript Validator from your .project file party, thus removing its validation powers.

Fine-tuning per project settings

Eclipse also lets you adjust the settings individually for each project depending on its unique requirements:

1. Project Properties -> JavaScript > Include Path.
2. Personalize each setting as per the project's needs.

You might want to change your global settings too:

1. Navigate to Eclipse Preferences -> Validation.
2. Find JavaScript Validator and adjust as needed.

Keep in mind, sometimes just hitting Suspend All Validators might not cut it. In some unique scenarios, disabling JavaScript support altogether can be a lifesaver, especially if you need to quickly squash JQuery library errors.

Things to consider while troubleshooting errors

If there are stubborn validation issues that persist, consider these additional steps:

Cleaning the .jsdtscope file

Pesky inclusion paths or incorrect configurations hiding in your .settings/.jsdtscope file can cause unwanted validation. This is where Eclipse stores include path information, so a less-than-perfect configuration can lead to undesired outcomes.

Tackling Eclipse preferences

In Eclipse, visit Windows > Preferences > Validation to find additional validation settings:

1. Tweak Defer validation until manual build to control when validation triggers kick in.
2. Uncheck Build and Manual for JavaScript validation to reduce workspace noise.

Remember, the Suspend All Validators option isn't always the hero you need. Sometimes it only suspends new validations without removing existing markers. Regularly updating Eclipse along with its plugins might help, as newer versions can include bug fixes and improvements that solve these irksome errors.

After making your changes, it's a good idea to clean your project for a fresh start:

1. Menu -> Project -> Clean....
2. Choose your project(s) and click Clean.