type less css in your sbt projects
a friendly companion for coffeescripted-sbt
less # compiles less source files
charset(for less) # character encoding used in file IO (defaults to utf-8)
mini(for less) # setting for compiled minification (false by default)
filter(for less) # filter for files included by the plugin
exclude-filter(for less) # filter for files ignored by the plugin
unmanaged-sources(for less) # lists resolved less sources
clean(for less) # deletes compiled css
config:source-directory(for less) # where less files will be resolved from
config:resource-managed(for less) # where compiled css will be copied to
In your plugin definition add
addSbtPlugin("me.lessis" % "less-sbt" % "0.1.5")
And in your build file add
seq(lessSettings:_*)
This will add less settings for the Compile and Test configurations.
To add it to other configurations, use
seq(lessSettingsIn(SomeOtherConfig):_*)
Put your .less files under src/main/less and find the compiled css under path/to/resource_managed/main/css
To overide a setting like mini, add something like following to your build file after including the less settings.
(LessKeys.mini in (Compile, LessKeys.less)) := true
To change the default location of less compiled css files, add the following to your build file
(resourceManaged in (Compile, LessKeys.less)) <<= (crossTarget in Compile)(_ / "your_preference" / "css")
working with @imports
Some less projects, like Twitter's Bootstrap project contain one main .less file which imports multiple .less files using the @import feature of less. To acheive the same kind of compilation with less-sbt, make the set the filter defined by less-sbt to the target of compilation
(LessKeys.filter in (Compile, LessKeys.less)) := "your_main.less"
This will build a single your_main.css file.
To see an example of compiling Bootstrap itself, check out the scripted test.
Note that using this style of design in combination is sbt's continuous execution operator, ~, will not trigger less if the primary less file's dependencies change. This is a known issue.
All available keys are exposed through the LessKeys module.
Have an issue? Tell me about it
I'll take them where they make sense. Please use a feature branch in your fork, i.e. git checkout -b my-cool-feature, and if possible, write a scripted test for it.
Doug Tangren (softprops) 2011