Hi Manos, Thanks for the information; I am familiar with jstools. Again, my intention here though is not to bundle "all things JavaScript" into one plugin. I think that jstools does this as per the Maven JavaScript plugin. My approach is to offer plugins focused at one specific area of functionality and then have various archetypes available that pull in plugins for common use-cases.
'happy to be educated further of course. Thanks again. Kind regards, Christopher On 20/10/2010, at 7:05 PM, Manos Batsis wrote: > On 10/19/2010 11:39 PM, Christopher Hunt wrote: >> think my largest issue is that it is prescriptive about all tools used >> in the JS dev cycle; it feels similar to having something like a "Maven >> Java Tools" (which of course we don't have as a single plugin). >> >> My intention is to develop and use other JS plugins within the dev cycle >> just as I would when developing Java based software. For example I'd >> like to utilise plugins for JSLint, JSTestTools and YUI Compressor. >> > > Haven't followed the thread, but you'll probably find the jstools plugin [1] > goals useful. We use it to produce JSLint, JSDoc and YUI Doc reports (the > latter is available on the trunk). > > We also use the mobilvox js plugin [2] for compression. A sample POM that > uses both is avalable in sarissa [3] javascript library. > > [1] http://dev.abiss.gr/mvn-jstools/ > [2] http://ossi.mobilvox.com/maven-js-plugin/ > [3] http://dev.abiss.gr/sarissa/installation.html > > hth, > > Manos --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
