We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are in the midst of a 2-day+ javadoc.io outage, see maxcellent/javadoc.io#180. This is not the first time unfortunately 😕
We currently use javadoc.io URLs by default both for inter-API linking and also on documentation websites.
However, because we are publishing our docs to Sonatype/Maven, they are also available at a Sonatype-hosted URL. For example:
https://s01.oss.sonatype.org/service/local/repositories/releases/archive/org/typelevel/cats-docs_2.13/2.10.0/cats-docs_2.13-2.10.0-javadoc.jar/!/index.html
We might consider switching to using the Sonatype URLs in all the places.
Pros:
Cons:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We are in the midst of a 2-day+ javadoc.io outage, see maxcellent/javadoc.io#180. This is not the first time unfortunately 😕
We currently use javadoc.io URLs by default both for inter-API linking and also on documentation websites.
However, because we are publishing our docs to Sonatype/Maven, they are also available at a Sonatype-hosted URL. For example:
https://s01.oss.sonatype.org/service/local/repositories/releases/archive/org/typelevel/cats-docs_2.13/2.10.0/cats-docs_2.13-2.10.0-javadoc.jar/!/index.html
We might consider switching to using the Sonatype URLs in all the places.
Pros:
Cons:
The text was updated successfully, but these errors were encountered: