=== What steps will reproduce the problem (please be specific and use wikiformatting)? ===
% touch help.scala
% fsc help.scala
% mkdir -p new&& mv help.scala new% cd new% fsc help.scala # this should build help.scala in directory "new"error: source file 'help.scala' could not be found
one error found
% mv help.scala ..
% fsc help.scala # here help.scala relates to ../help.scala
=== What is the expected behavior? ===
When running fsc from a different directory.. if there is already a scala compiler daemon running then it should inherit the new current working directory of fsc.
=== What do you see instead? ===
When running fsc, if there is no scala compiler daemon running it is run with the current working directory of fsc, but keeps this PWD for all subsequent runs until the daemon exits, even when subsequent fsc invocations are from different directories.
=== What versions of the following are you using? ===
Java: OpenJDK 1.6.0_22
Operating system: Linux 2.6.37
The text was updated successfully, but these errors were encountered:
@JamesIry said (edited on Jan 17, 2013 4:15:18 PM UTC):
The fix is pretty simple, just be sure to make source file names absolute based on the client's working directory. JamesIry/scala@6744cbb . What's missing from that commit is a good automated test.