-
Notifications
You must be signed in to change notification settings - Fork 49
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
Incorrect scaladoc links to JDK apidocs #592
Comments
Hmm, maybe we forgot to prefix it with sbt-typelevel/settings/src/main/scala/org/typelevel/sbt/TypelevelSettingsPlugin.scala Line 370 in 1f6850a
|
No, that seems fine. So now I suspect maybe we are not mapping the right thing 🤔 sbt-typelevel/settings/src/main/scala/org/typelevel/sbt/TypelevelSettingsPlugin.scala Line 388 in 1f6850a
FTR that's cargo-culted from here. |
I think we should try refreshing our cargo-cult with exactly whats in Scala.js, for example this part seems interesting. |
Tried fixing this in 4b8962b but it didn't fix Choam 😕 so either we're still not doing it right, or perhaps sbt is overriding us. |
Thanks for trying! This whole apiMappings setting is very mysterious to me, so I don't have any ideas... |
Edit: what I wrote above is incorrect, I still don't understand what's happening. |
There is a strange interaction with the |
Aha, I see, thanks for investigating. But this does illustrate our setting is not really doing anything. |
Links to JDK APIs in the generated scaladoc seem to be incorrect. Two examples:
java.security.SecureRandom
links to https://docs.oracle.com/en/java/javase/11/docs/api/java/security/SecureRandom.html (which is a dead link).java.util.concurrent.atomic.AtomicReference
links to https://docs.oracle.com/en/java/javase/17/docs/api/java/util/concurrent/atomic/AtomicReference.html (which is also a dead link).In theory this can be an sbt/scaladoc bug, but I see some settings here, which seem related, but somehow they're not applied(?).
The text was updated successfully, but these errors were encountered: