-
Notifications
You must be signed in to change notification settings - Fork 21
Scaladoc external references jdk11 #10675
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
Here is a workaround that we've been using in the Scala.js build for a while: https://github.com/scala-js/scala-js/blob/aede3c83fc6ab9132f475b98a662d0aaaa77dfb8/project/Build.scala#L233-L237 |
Ok, good to know. Thank you. I gave your hack a go in ThoughtWorksInc/sbt-api-mappings#14. |
Looks like the hack works for 2.12, but not 2.11.12 for some reason. Is that your experience as well? |
Well we have scala-js/scala-js#3152, but otherwise it seemed like it was working fine (for other projects in our build, beside |
Ok, I tried looking through the Jenkins builds for scalajs, but I don't think Java 9 is in the matrix. I'll try the library project locally on Java 9.... Yeah, doesn't look like the hack works on 2.11 |
This probably won't be fixed, but works in 2.12. It doesn't work again in 2.13, but this can be superseded by #11839. |
It's no longer possible for scaladoc to reference the Java class library from Java 9, now, which was discovered here ThoughtWorksInc/sbt-api-mappings#8 by the Akka team. The Akka docs have a few Java refs in their api docs, e.g. https://doc.akka.io/api/akka/current/akka/japi/Util$.html
Presumably, the Java-9
rt.jar
hack would work from scala/scala-dev#139, but in the long-term scaladoc will needmodule-path
support and a way to point to modules likejava.base
...The text was updated successfully, but these errors were encountered: