Hi team,
I've written another JavaScript related plugin; this time for JSLint. I'd like
to solicit your interest in my submitting this one to the sandbox.
I realise that there are of course other MOJOs out there that perform JSLint
goals. However I felt that they were:
a) bundled as part of something larger (compression for example);
b) intended for project reporting (as distinct from being available while
editing source); and/or
c) not optimised for efficiency (linted all files, not just ones that had been
modified - big problem for large projects).
The plugin I've developed operates quickly and efficiently on modified
JavaScript source code. When used with IDE's such as Eclipse and its Maven
integration, developers can rapidly see JSLint problems reported in the IDE's
console as a JavaScript source file is saved. Nothing special was required here
as the plugin binds to the process-sources and process-test-sources phases. As
you may know, when you save a resource under m2eclipse the process-resources
goal is fired.
From a development perspective the plugin is complete and I've rigidly followed
the development guidelines.
Is there interest in my submitting this to Codehaus?
Kind regards,
Christopher
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
