You can clone with
In debug mode, lesscss-resources serves raws less files, but IMHO, I can't find any interest in this. My point is that .less files should be rendered, even in debug mode.
I had a similar discussion with Francis McKenzie, one of the author of gsp-resources plugin. For that plugin, there was no point in not processing, for example, xxx.css.gsp in xxx.css in debug mode. He felt agree with me and found a way to do this:mckenfra/gsp-resources@5a8930f
For me, the main reason to use debug mode is to enable in-browser debugging, as resources are not bundled, nor minified.
Before using lesscss plugin, I was always using resources debug mode while in dev execution environment. And this way of doing is suggested in the resources plugin doc : "You can specify this value per-environment in your Config."http://grails-plugins.github.com/grails-resources/guide/8.%20Debugging.html
What do you think?
+1 to florent-blanvillain for this suggestion
webdev workflow is painful working with edits to imported .less files not triggering rebuilt .css