New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scala scripts calling each other from sub-shells #4099
Comments
Imported From: https://issues.scala-lang.org/browse/SI-4099?orig=1 |
@hubertp said: |
@lindydonna said: |
help wanted... consigning fsc to the dustbin of history |
Closing in favor of future tickets about the REPL protocol and REPL server. "fsc who?" |
=== What steps will reproduce the problem (please be specific and use wikiformatting)? ===
I've got a pair of scala scripts one that calls the other like this
minimized example:
script: a
script: other/b
This assumes that a is in some path like: /tmp and b is in /tmp/other and commons-email-1.2.jar and commons-io-1.4.jar are in those same paths respectively.
=== What is the expected behavior? ===
=== What do you see instead? ===
=== Additional information ===
If I run with -verbose, it shows that the classpath is correct for 'b'
but not for 'a' when the exec is performed. In both cases, scala
starts a new compile server instance (reason = "settings not equal").
When I change the exec line in 'a' by adding '-nocompdaemon' the error
goes away.
See below for discussion:
http://scala-programming-language.1934581.n4.nabble.com/scala-scripts-calling-each-other-is-this-a-bug-td3094846.html
=== What versions of the following are you using? ===
The text was updated successfully, but these errors were encountered: