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
REPL: load transitive dependencies of JARs on classpath #6660
Comments
Imported From: https://issues.scala-lang.org/browse/SI-6660?orig=1 |
Li Haoyi (lihaoyi) said: @ load.ivy("com.lihaoyi" %% "upickle" % "0.2.6")
:: resolving dependencies :: com.lihaoyi#upickle_2.11-caller;working
confs: [default]
found com.lihaoyi#upickle_2.11;0.2.6 in central
found org.scala-lang#scala-library;2.11.4 in central
[2.11.4] org.scala-lang#scala-library;2.11.4
found org.spire-math#jawn-parser_2.11;0.7.0 in central
found com.lihaoyi#acyclic_2.11;0.1.2 in central
found org.scala-lang#scala-compiler;2.11.0 in central
found org.scala-lang.modules#scala-xml_2.11;1.0.1 in central
found org.scala-lang.modules#scala-parser-combinators_2.11;1.0.1 in central
found org.scala-lang#scala-reflect;2.11.4 in central
[2.11.4] org.scala-lang#scala-reflect;2.11.4
res17: Unit = ()
@ import upickle._
import upickle._
@ upickle.write(Seq(1, 2, 3))
res19: String = "[1,2,3]"
@ |
I wonder how the Dotty REPL does on this |
From outside the repl, it can be done with coursier (dwijnand/scala-runners#3), so there's some overlap here with the work discussed at scala/scala-dev#326. |
I thought this is what
Same result with |
and both jars at end of |
oh there is a fat comment
I'm not entirely sure why that is useful, as opposed to exposing the contents of the jar file. Who has a home chef to specially prepare anything? |
this is now scala-cli's job |
@som-snytt if you're planning something, I think Scala 3 is the appropriate first venue — though we could discuss... |
@SethTisue this is why I looking at that class path stuff! The tweak to The use case, per the OP, is that it simplifies running local jars. |
The Scala REPL should load dependencies referenced in MANIFEST.MF files of other JARs on the classpath.
As described in https://support.typesafe.com/tickets/1585:
The text was updated successfully, but these errors were encountered: