New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modifying resourceManaged doesn't appear to impact the plugin #1
Comments
Hi @sroebuck. Thanks for trying out the plugin. You are almost there :) First, a quick note on best practices. You should be noticing a change in how newer sbt plugins are developed and how keys are exposed. The collective plugin community and (with Marks input) have decided on a new design based on best practices. The old design used configs for namespaces which was kind of bastardizing what configs are for. So you should see less of this
and more of
While I agree thats less than ideal you should start seeing a new repl syntax for task dependent keys in upcoming sbt releases. Another part of the best practices doc is on reusing exisiting keys. There is no Keys are also used within provided scopes rather than custom scopes now. Below is want you want to use In your build file, add
which should result in the following repl behavior
Since changing the default location or where less css files are written to is probably a common question I'll add that to the readme as well. Have fun! |
Just wanted to thank for the explanation, and confirm that the following combo is now working perfectly:
|
I'm trying to change where the
css
files are compiled to in mybuild.sbt
file. For the CoffeeScriptedSbt plugin I can do this with a line like:This works fine.
With less-sbt I appear to have to write:
whilst this seems to change the setting, in that
target-directory(for less)
from the sbt prompt gives the right result, the less command nevertheless appears to compile to the same place as it did before.On the other hand, I find configuration in sbt to be a process of trail and error so I could be doing completely the wrong thing here.
The text was updated successfully, but these errors were encountered: