The warnings plug-in does not scan js files using the JSLint scanner. It only
visualizes the results from JSLint. I.e., you need to run JSLInt in your build.
And then the plug-in will pick up these results and visualizes these on the
build page.
Ulli
Am 29.08.2013 um 11:00 schrieb Giovanni
Hi,
I've setup a new project with the latest version of warnings plugin to scan
js file with the JsLint integrated scanner.
However, it looks like that the plugin is using the wrong scanner (an XML
one?), hence I've selected JsLint from the dropdown for files of type **/.js
The stacktrace I
