Skip to content
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

Closed
scabug opened this issue Dec 20, 2010 · 6 comments
Closed

scala scripts calling each other from sub-shells #4099

scabug opened this issue Dec 20, 2010 · 6 comments
Labels
Milestone

Comments

@scabug
Copy link

scabug commented Dec 20, 2010

=== 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

#!/bin/bash -v

(cd other; b)
exec scala -cp commons-email-1.2.jar "$$0" "$$@"
!#
import org.apache.commons.mail._;

script: other/b

#!/bin/bash -v

exec scala -cp commons-io-1.4.jar "$$0" "$$@"
!#
import org.apache.commons.io.FileUtils._;

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? ===

$$ a
#!/bin/bash -v
(cd other; b)
#!/bin/bash -v
exec scala -cp commons-io-1.4.jar "$$0" "$$@"
exec scala -cp commons-email-1.2.jar "$$0" "$$@"
$$

=== What do you see instead? ===

$$ a
#!/bin/bash -v
(cd other; b)
#!/bin/bash -v
exec scala -cp commons-io-1.4.jar "$$0" "$$@"
exec scala -cp commons-email-1.2.jar "$$0" "$$@"
/tmp/./a:7: error: value apache is not a member of package org
import org.apache.commons.mail._;
          ^
one error found
$$

=== 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? ===

  • Scala: 2.8.1.final
  • Java: Java(TM) SE Runtime Environment (build 1.6.0_22-b04-307-10M3261)
  • Operating system: MacOS 10.6
@scabug
Copy link
Author

scabug commented Dec 20, 2010

Imported From: https://issues.scala-lang.org/browse/SI-4099?orig=1
Reporter: s wade (swadenator)

@scabug
Copy link
Author

scabug commented Jan 4, 2011

@hubertp said:
Paul, you seem to be messing with the scripts in the past. Would you mind having a look? (if not the please reassign).

@scabug
Copy link
Author

scabug commented Jan 4, 2011

@paulp said:
This sounds like a re-run of #1683. fsc is fragile and we have pretty much zero tests for either scripts or fsc directly. I am not up for working on either of those things until we have some real testing infrastructure which can backstop the work.

@scabug
Copy link
Author

scabug commented Jan 25, 2011

@lindydonna said:
It would be good for this to be fixed, but there are insufficient resources on the team. Reassigning to community.

@scabug scabug added this to the Backlog milestone Apr 7, 2017
@SethTisue SethTisue added fsc and removed help wanted labels Mar 3, 2018
@SethTisue
Copy link
Member

help wanted... consigning fsc to the dustbin of history

@som-snytt
Copy link

Closing in favor of future tickets about the REPL protocol and REPL server.

"fsc who?"

@SethTisue SethTisue modified the milestones: Backlog, 2.13.0 Aug 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants