On Mon, Nov 30, 2009 at 2:37 PM, Mark Volkmann <[email protected]>wrote:
> Ah ... I can see that. One thing I recommend is making jslint part of > an automated deployment process. I set up mine so that every time I > deploy my web app it looks for JavaScript source files that have been > modified since the last deploy. It runs jslint on those and the deploy > fails if any issues are reported. That has saved me a lot of debugging > time. Still, as you say, there is room for improvement. > Plug, plug: http://code.google.com/p/jslint4java/ It's just a small wrapper that lets you run jslint as part of an ant build, or from the command line. I've found it quite handy in past jobs. -Dom -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
