On 04/29/2012 10:46 PM, Daniel Becroft wrote: > On Wed, Mar 21, 2012 at 6:34 PM, timos <timo.j.sillan...@gmail.com > <mailto:timo.j.sillan...@gmail.com>> wrote: > > The same problem here. At file system level I can see a generated > jshint.xml file containing the JSLint errors, a violations/ > violations.xml file and violations/file/<js file name and path>.xml > files but still each file specific link leads to a blank page. > > Any updates on this? Was anyone able to resolve the problem? > > > I'm still having no luck. I'm using stylecop/fxcop instead of JSLint, > but I still have the issue. > > A few things to note: > 1) The build is performance on a slave node (not the master) > 2) For FxCop, where the link is to a .cs file, I get the code snippets > highlighted with the errors, but I don't get anything about the error > text listed above. But if the link is to a class, I get a blank page > (with just the violations icon). > > It's really getting annoying. Is there anywhere else we should be > raising this?
During the integration of the violations parsers (JSLint, FXCop, etc.) into the warnings plug-in I noticed that the parsers are not serializable. Maybe this is the reason for the behavior. Does the plug-in work on the master? In order to have a working JSLint parser on a slave (for my warnings plug-in) the parsers should be made serializable... Ulli
