These are chat archives for sbt/sbt-native-packager

6th
Oct 2015
Aleksej Ruckoj
@aruckoj
Oct 06 2015 07:46
@muuki88 @fiadliel Thanks guys
Richard Gomes
@frgomes
Oct 06 2015 08:56
@muuki88 : I'm trying to run Star5SafeJvm/universal:packageBin from my plugin, the same way SBT does when you type it on the command line. Something (pseudo-code) like this: (packageBin in config).run(projectRef, buildStructure, state). I cannot do (packageBin in universal).run(refStar5SafeJvm, ...) because my plugin does not know sbt-native-packager, it only receives a string saying Star5SafeJvm/universal:packageBin. So, I guess I will have to understand how SBT parses commands and run them.
Richard Gomes
@frgomes
Oct 06 2015 09:13
@muuki88 :: it's here: Command.process("Star5SafeJvm/universal:packageBin", state)
Justin Kaeser
@jastice
Oct 06 2015 10:28
In the Docker plugin, what is the difference between Cmd and ExecCmd?
Gary Coady
@fiadliel
Oct 06 2015 10:55
@jastice ExecCmd creates a command making use of the "exec" form of running a process, e.g. RUN ["/bin/bash", "-c", "echo hello"] - see the RUN reference in https://docs.docker.com/reference/builder/
Justin Kaeser
@jastice
Oct 06 2015 12:20
@fiadliel ah, so ExecCmd("ADD", "a", "b") is equivalent to Cmd("ADD", "a b") ?
Gary Coady
@fiadliel
Oct 06 2015 13:19
Not exactly, actually I wonder if Cmd should add quotes around its parameters... it currently would do ADD a b rather than (maybe more correctly) ADD "a b". Whereas ExecCmd will do ADD ["a", "b"] - note the JSON array syntax.
Justin Kaeser
@jastice
Oct 06 2015 13:21
Got it. but semantically the same thing, right?
Gary Coady
@fiadliel
Oct 06 2015 14:25
Nope; well at least for things that execute commands, one runs the command inside a shell, the other uses exec directly.
Justin Kaeser
@jastice
Oct 06 2015 14:28
oh okay.
another thing. I want to put a .war into a tomcat docker image. What is the context that gets passed to the docker builder? target/docker?