mal/impls/scala/assembly.sbt

import sbtassembly.AssemblyPlugin.defaultShellScript

test in assembly := {}
assemblyJarName in assembly := "mal.jar"
mainClass in assembly := Some("stepA_mal")
assemblyOption in assembly ~= { _.copy(prependShellScript = Some(defaultShellScript)) }
scala: fix w/ xenial, sbt 0.14.6, update build. Build had become out of date so update docker image to xenial and sbt to 0.14.6 and update Scala build files to go with new sbt version. 2018-07-12 21:51:02 +03:00			`import sbtassembly.AssemblyPlugin.defaultShellScript`
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00
			`test in assembly := {}`
scala: fix w/ xenial, sbt 0.14.6, update build. Build had become out of date so update docker image to xenial and sbt to 0.14.6 and update Scala build files to go with new sbt version. 2018-07-12 21:51:02 +03:00			`assemblyJarName in assembly := "mal.jar"`
scala: Run steps directly from jar file The Scala build will create a mal.jar file with all the steps' classes in it. A `run` wrapper script will run that jar with a specific step main class according to the `$STEP` environment variable. Now the jar file is created only once (when testing step0) and then re-used for testing the next steps, which should speed up the build. Moreover, sbt now prepends shell script header to the jar file, so no need to implement this in Makefile (for the `dist` target). 2016-05-16 18:25:42 +03:00			`mainClass in assembly := Some("stepA_mal")`
			`assemblyOption in assembly ~= { _.copy(prependShellScript = Some(defaultShellScript)) }`