We have a build that compiles 30 sites of common css into site specific themes. This build runs inside a lesscss plugin for maven that takes 2:24 to build every

We have a build that compiles 30 sites of common css into site specific themes. This build runs inside a lesscss plugin for maven that takes 2:24 to build everything. It does them one at a time and seems to throw away commonly compiled bits regularly. When we dont need new css, we pass a profile disable that wraps the css compile. This may be an extreme case, but most of it seems avoidable with normal cascades. My front end people want the "convenience" of less, but they dont consider the cost until it hurts their build times.