5

In my project build definition the SettingKey useProguard in the Android scope is set to true. This is what I want by default. When I execute one particular task, however, I want useProguard to be false. Everything in the Android scope comes from the sbt-android-plugin.

I'm not sure how best to solve this problem. From what I read it seems like a command can get the job done, since it can execute a task with a different state than what your current session sees. I tried to create such a command like so:

def buildWithoutProguard = Command.command("build-without-proguard") { state =>
  val extracted = Project.extract(state)
  import extracted._

  val transformed = session.mergeSettings :+ (useProguard in Android := false)
  val newStructure = Load.reapply(transformed, structure)
  val newState = Project.setProject(session, newStructure, state)
  Project.evaluateTask(buildAndRun, newState)
  state
}

I'm appending the command to my project settings and running the 'build-without-proguard' command executes the buildAndRun task as desired. However, useProguard is still true instead of false as I would expect.

First, this whole approach feels heavy handed to me. Assuming changing sbt-android-plugin isn't an option here then how else would I solve this problem?

Second, why doesn't this approach work as is?

bstpierre
  • 30,042
  • 15
  • 70
  • 103
James
  • 3,312
  • 1
  • 21
  • 15
  • possible duplicate of [How to change setting inside SBT command?](http://stackoverflow.com/questions/14262798/how-to-change-setting-inside-sbt-command) – Jacek Laskowski Jan 09 '14 at 22:52

1 Answers1

2

From what I understand from your question, you want the setting to be different for a dependency depending on what is depending on it. This doesn't make sense -- a dependency either is satisfied or it isn't, and what depends on it doesn't come into the equation.

Your solution seems satisfactory to me. An alternative would be making two projects, pointing to the same source, but with different proguard settings and different target, so one would build with and the other without proguard, and both would keep their state. You'd then do whatever you want just switching the projects.

Daniel C. Sobral
  • 295,120
  • 86
  • 501
  • 681
  • Hi Daniel, thanks for the answer. Separate project indeed seems to be the way to go. I'm still curious why the command doesn't work as it seems like it should. – James Jan 20 '12 at 02:05
  • Doesn't the task axis do something like "change the dependency based on what is depending on it"? If you have a task that depends on a setting, can't the setting can have different values depending on what task is running? – James Moore Oct 12 '13 at 18:35
  • @JamesMoore No, it doesn't, and no it can't. – Daniel C. Sobral Oct 14 '13 at 04:38
  • 2
    A setting can be scoped to a particular task, actually — but only if that task expects it to be (in other words, if that task's author coded it to look the key up in its own scope). – Seth Tisue Apr 11 '14 at 12:35