jshint-eclipse

Version 0.10.1 published

For details, please see the github release page.

Version 0.10.0 published

For details, please see the github release page.

Version 0.9.10 published

For details, please see the github release page.

Version 0.9.9 published

For details, please see the github release page.

Version 0.9.8 published

Project specific configurations are now read from a .jshintrc file in the project root. This allows to share configurations with other tools.

JSHint configuration files are simple JSON that contains options for JSHint and global variables. Details on the format and available options can be found on the jshint pages.

This configuration format replaces the “options” and “globals” settings. The JSHint property pages allow to edit the config files directly and initialize them with the old project settings.

In order to support this configuration style, it was necessary to drop support for legacy JSLint.

Version 0.9.7 published

Just a minor update to fix the severe performance drop that has been introduced in the recent version by including jshint 1.1.0. The problem has been fixed in jshint and the performance is back to normal.

A bug that prevented the plug-in from starting in Eclipse 3.6 has been fixed.

Builds can now be cancelled if they take too long. Thanks John.

The built-in JSHint has been upgraded to version 2.1.2.

Version 0.9.6 published

This version adds support for non-boolean options such as indent, maxparams, maxdepth, etc.

A bug that caused a runtime exception for certain input files has been fixed.

The built-in JSHint has been upgraded to version 1.1.0.

Version 0.9.5 published

This is a bugfix release, it updates the built-in JSHint and fixes a number of issues such as an off-by-one shift in marker positions and a problem with wild JSHint errors caused by an interference with another rhino version in the IDE.

The built-in JSHint has been upgraded to version r12.

Version 0.9.4 published

This update introduces a new way of selecting the files and folders to be validated, based on include and exclude patterns. This allows for finer-grained control, e.g. including all *.js files but excluding *.min.js files, or excluding files in a build target folder.

The include and exclude patterns must be configured in the project’s properties, but a global preference page is planned for a future version.

The built-in jshint has been updated to the newest version r07.

A bug that prevented jshint-eclipse from running on Eclipse 3.6 has been fixed.

Version 0.9.3 published

The options for JSHint can now be shared among all projects in the workspace. A new preference page “Options” has been added for the shared options. It’s still possible to have project-specific options, but (following the established pattern in Eclipse) that’s not the default anymore.

If you’ve already defined options for certain projects and want to keep them in the projects, you’ll have to check the new checkbox “Enable project specific settings” in the project’s property pages. A full rebuild of the workspace is recommended after updating jshint-eclipse to ensure that all markers are up-to-date: Project > Clean... > Clean all projects.

A bug has been fixed that prevented JSHint from succeeding and lead to annoying error messages.

Version 0.9.2 published

The JSHint Eclipse integration can now be used with a custom version of JSHint. A preference page has been added that allows to select a jshint.js file from disk. The original JSLint is also supported.

The built-in default library has been upgraded to the latest JSHint version (r06).

The Mozilla Rhino library is no longer contained in the core plug-in, but included as a separate plug-in.

Version 0.9.1 published

To be able to run the JSHint checker headless from Java code, the plug-in has been split into a core and a ui bundle. The core bundle has a simple API that can be used as follows:

JSHint jshint = new JSHint();
jshint.load();
jshint.configure( new Configuration() );
jshint.check( jsCode, new ProblemHandler() { ... } );

As a result, the ui plug-in’s id has changed, so that configurations created with the previous version have to be updated. The plug-in will do this automatically.

A problem with wrong marker positions when using tabs has been fixed.

Version 0.9.0 published

After some early builds for my own use in the RAP project, I’m quite satisfied with the current state and think that this plug-in may already be helpful to others, too. So I decided to move this project to EclipseSource, which will be a better home in the long run, created this site, and made a first version available.

Apart from its humble feature set, I’m not aware of any bugs. I’m happy to receive feedback, also bug reports and contributions are welcome.