Closed scabug closed 12 months ago
Imported From: https://issues.scala-lang.org/browse/SI-9842?orig=1 Reporter: @szeiger Affected Versions: 2.12.0-M5
@felixmulder said (edited on Aug 7, 2016 9:32:11 AM UTC): If I understand your usecase correctly - you're referencing documentation for both 2.11 and 2.12 and you want to be able to use the same links?
In #9873 I explain why the the scheme was changed.
I believe this particular compatibility issue could be solved by producing both an "index.html" and a "package.html" for the package objects.
Out of curiosity I'd love to know where in your documentation this is an issue :)
EDIT: saw the travis link just now
@szeiger said: It's not a big issue, at least not for Slick. We can do a hard switch-over from 2.11 scaladocs to 2.12 scaladocs at a later point. We only publish one set of scaladocs (and manual) anyway, so for now we still publish the 2.11 version and don't bother verifying links on 2.12.
@Atry said (edited on Nov 7, 2016 6:20:27 AM UTC): New scaladoc still generates old URL to external dependencies.
For example: Binding.scala's API documentation contains many old style links to Scala standard library, e.g. http://www.scala-lang.org/api/2.12.0/index.html#scala.concurrent.Future . All the links are broken.
Migration from Scaladoc 2.11 is unlikely to receive further attention.
The old (2.10/2.11) scaladoc used to put type aliases in package objects into "package.html", the new one uses "index.html", thus making it impossible to link correctly to these members when cross-building on 2.11 and 2.12.
See https://travis-ci.org/slick/slick/builds/142174330 for a failure caused by this.
On 2.11, you can link to
which gets redirected to
On 2.11.0-M5 you need
There doesn't seem to be a link format that works for both versions.