-
Notifications
You must be signed in to change notification settings - Fork 92
scala-xml repo has sbt console errors #313
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
Comments
@smarter your dept, or can you recommend someone else from the Dotty team who could look at it? |
sbt-dotty tries very carefully to not affect non-dotty projects, but turns out that we're doing it wrong and I don't know if there's a way to do it right: https://gitter.im/sbt/sbt-contrib?at=5cea7db4ad024978c62ff208. I'll look into it. |
Thanks for looking into it. These aren't fatal errors. The Scala REPL does seem to work. However the errors would seem to hint at other problems. For one, we can no longer use XML literals:
It seems this is because the library code is generally unreachable:
Using the JVM sub-project,
|
See scala/scala-xml#313 for example. No test because apparently there's no way to properly test "sbt console" from scripted tests: https://github.com/sbt/sbt/blob/b6f02b9b8cd0abb15e3d8856fd76b570deb1bd61/sbt/src/sbt-test/project/console/test#L7
See scala/scala-xml#313 for example. No test because apparently there's no way to properly test "sbt console" from scripted tests: https://github.com/sbt/sbt/blob/b6f02b9b8cd0abb15e3d8856fd76b570deb1bd61/sbt/src/sbt-test/project/console/test#L7
Fixed by #314. |
@eed3si9n maybe you should take a gander at dotty-staging/dotty@d46235b |
@SethTisue He reviewed the PR already :) |
@SethTisue Yea. Both Dale and I have reviewed scala/scala3#6577 |
However, I do appreciate the "hey Eugene maybe you should look at this" signals. |
oh sorry, I only looked at the commit without looking at the PR :-) |
Seems after merging #312, starting the console in sbt causes issues:
If I disable the sbt-dotty plugin, it doesn't happen.
The text was updated successfully, but these errors were encountered: