Fix classpath in QuoteDriver when executing from sbt

[nicolasstucki]

No description provided.

[nicolasstucki]

Found the bug and fixed it in nicolasstucki/scala-quoted-util@39087d4

[smarter]

I have no idea what the context is so I can't really review this. I'll just note that you can pass -usejavacp to the compiler so that the Scala classpath contains the Java classpath.

[nicolasstucki]

Maybe the -usejavacp solves this issue cleanly. I will try it out.

[nicolasstucki]

The -usejavacp did not work, the issue is that in this case the java classpath does not contain the current classpath. The classpath only contains the SBT launcher which then uses a custom classloader to load the classpath that will be used to run the application.

[allanrenucci]

the classes loaded by

[allanrenucci]

in the property

[nicolasstucki]

Rebased and fixed comments

[smarter]

What about using ctx.settings.classpath instead, isn't that enough?

[nicolasstucki]

No, the classpath of the library in not in there. That is why I needed to add it explicitly. We also need the current classpath in case the quote refers to something in the application (such as class or static method).

[nicolasstucki]

For example

class Foo
object Foo {
  def main(...) = {
    val q = '(new Foo)
    q.run // Foo need to be present in the classpath of the compiler that will compile q
  }

[liufengyun]

In scala.reflect macros, it assumes separation (ahead-of) compilation of macro definitions. The user-app must depend on the lib that contains Foo in order to use that macro, thus it's automatically on the path.

[nicolasstucki]

Same here. But the app is guaranteed to have separate compilation as the macro is staged.

[smarter]

I assume macros in scalac have the same problem. We should check how they handle classpaths.