Fixes to run SanityCheck on Windows 10

[lopezavila85]

Hello,

I have updated some dependencies in the Build.scala file which give an error when the sbt assemblycommand is issued - I think those were Scala to 2.11.7 and Algebird to 0.11.0.

Then, I execute scala run scripts/SanityCheck0.scala, but the scalac invocation gives an IOException saying the scalac command is not found. I have tried to write the "full path", but I don't know which is the correct form. In my case, I have scala, scalac, etc. in C:\Program Files (x86)\scala\bin

The line which throws the exception is:
val compilecmd = s"scalac -deprecation -cp $assembly${pathSeparator}$libs -d classes $script"
Regards.

[deanwampler]

I think there's an issue on Windows where the Scala process API doesn't have access to the full environment, such as your path. You could edit the definitions of compileCmd and runCmd at the end of the run script to add the full paths to scalac and java, respectively.

I took a look at updating this workshop. Perhaps this weekend I'll see if there is a newer, better way to run Scalding than this old approach.

[deanwampler]

Try the updates I pushed today and see if it works better on Windows. You might stll need to add the paths to the commands.