-
Notifications
You must be signed in to change notification settings - Fork 21
Scaladoc has unnecessary dependencies on scala-parser-combinators and scala-xml #9560
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
Imported From: https://issues.scala-lang.org/browse/SI-9560?orig=1 |
@retronym said: |
@SethTisue said: |
@soc said: |
@lrytz said: |
@szeiger said: |
@dwijnand said: |
@SethTisue said: |
So presumably the HTML bit is because of Scaladoc.
Is this talking about XML literals or is there a third situation? |
yup
I'm not sure what Jason was thinking when he said that. We can cross that bridge when we come to it, if there's even a river left to cross. |
scala-library-all no longer exists in 2.13, so that's one less thing we need to worry about here |
It would seem the compiler could still be built without a scala-xml dependency and preserve XML literal support, but I suppose the issue is being able to rip out the dependency from the compiler test suite, which see scala/scala@5b532e9 is a commit from Adriaan from Nov-14 2013 that put back the tests for scala-xml back when the community module work was done. It looks like the scala compiler junit test suite doesn't seem to need scala-xml as a dependency. Presumably, this is because those junit tests were able to be moved to the scala-xml repo. |
scala/scala#6436 has finished this off. |
in both cases we could avoid replacing one Scala dependency with another Scala dependency by just using plain Scala and/or by adding a Java dependency.
main benefit is reduced complexity in the build.
see discussion at scala/slip#24 (comment) and https://gitter.im/scala/slip?at=564a3a2e8b242470793e3035 (for HTML generation, Haoyi thought "vendoring a small 1000loc subset of scalatags" was plausible)
also I discussed this with retronym just now and:
The text was updated successfully, but these errors were encountered: