in that case maybe we should start something similar to c-build[1] or groovy/gmaven (which already has been moved out of the codehaus repo). Until then the mojo-sandbox seems to be the right place to evolve such project. - Robert [1] http://svn.codehaus.org/mojo/c-builds/trunk/
From: hu...@internode.on.net Date: Wed, 20 Oct 2010 07:39:55 +1100 To: user@mojo.codehaus.org Subject: Re: [mojo-user] Proposal for a Maven JavaScript Import Plugin at Codehaus On 20/10/2010, at 2:53 AM, Robert Scholte wrote: sounds like it should be added to the javascript-maven-tools[1] I tried using that and I must confess to not getting along with it. I 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. Thanks for the feedback. Please keep it coming. Kind regards, Christopher
