Def.taskDyn (and inputTaskDyn) are undocumented
#999
Comments
|
and here's a sample usage of the exotic, elusive creature known as and another: http://stackoverflow.com/questions/20091719/getting-settings-and-arguments-with-sbts-inputtask/ |
ghost
assigned
harrah
added a commit
that referenced
this issue
Nov 27, 2013
harrah
added a commit
that referenced
this issue
Mar 21, 2014
adleong
added a commit
to linkerd/linkerd
that referenced
this issue
Jun 14, 2016
# Problem The run task on the linkerd example configurations does not accept arguments: ``` $ ./sbt 'linkerd-examples/transit:run --log.level=DEBUG' [info] Loading project definition from /Users/alex/workspace/linkerd/project [info] Set current project to all (in build file:/Users/alex/workspace/linkerd/) [error] Expected key [error] Expected '::' [error] Expected end of input. [error] linkerd-examples/transit:run --log.level=DEBUG ``` # Solution Parse arguments using "the exotic, elusive creature known as inputTaskDyn, with which even Stack Overflow cannot help you" (1) and feed them into `run`. (1) sbt/sbt#999
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
"I guess taskDyn still isn't documented is it. Maybe someone can open a bug and I'll try to get to it for 0.13.2" — @harrah on IRC just now
in the meantime the intrepid searcher can find glimmers of enlightenment at such places as:
http://www.scala-sbt.org/0.13.0/docs/Detailed-Topics/Tasks.html says "Dynamically changing the structure of the task graph is possible. Tasks can be injected into the execution graph based on the result of another task". in 0.12-land you do that with
flatMap, in 0.13 you use theDef.taskDynmacro instead.The text was updated successfully, but these errors were encountered: