On 26/10/2010, at 4:22 PM, nicolas de loof wrote: > Did you take alook at mojo js tools project ? > it allready has a JSlint goal Hi Nicolas,
Thanks for replying. Yes, I did take a look at your Mojo (http://mojo.codehaus.org/javascript-maven-tools/javascript-report-maven-plugin/jslint-mojo.html). Your Mojo being bound to the "site" phase (by default) fits into the "intended for project reporting" comment that I made. While I think there could be a place for JSLint site reporting, I personally see JSLint reporting being most useful at the point of code being written e.g. when a source file is saved. Hence the impetus for my plugin writing to the console and being efficient about being invoked frequently. > > maybe you could contribute/enhance the jstools with your plugin ? I'd love to. I'm wondering if your project: http://mojo.codehaus.org/javascript-maven-tools/index.html ...could benefit from becoming a great place to launch into JS development with Maven and have it introduce various JS Maven projects e.g. other Mojo's and not even just Codehaus ones. I also see a place where we need to come up with some new lifecycles (which I see you've approached) and perhaps your project is the place for that. Another thought is that some JS Maven archetypes could also possibly live under your project. My main thought though is that we should move away from having a one-size-fits all Mojo for JS tooling. As stated in other threads, we don't have all-encompassing Mojo's for Java, and so I don't think that we should have them for JS. Your thoughts? Kind regards, Christopher --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
