-
Notifications
You must be signed in to change notification settings - Fork 424
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
To add an ability to disable link to java documentation #188
Comments
See |
As far as I understand, ExternalDocumentationLinkResolver always opens a connection to the package list url (when the cached entry exists, it checks the modified date) and will fail when there is no network. |
It should show a warning, not fail when checking for modified date |
The error is ignored only when cached package list exists. To make workaround with |
Is there an update for http://docs.oracle.com/javase/9/docs/api/package-list ? |
I am behind proxy but still can create Javadoc out of Pojo application, so what so special with kotlin that it is it not letting us generate javadoc. |
proxy support would be added by #314 -Dhttp.proxyHost=host.domain.com if proxySet is true and proxyUser with proxyPassword is set then basic proxy authentication is added |
I think Dokka should not connect to the internet while building by default. I would rather see an option to enable stdlib links (that is disabled by default) than an option to disable stdlinks. But an option to disable stdlib links would be better than the current situation. I think it is reasonable to expect that when building, the only internet connections made are those made by the build system to configured endpoints (e.g.: Maven and SCM as configured in the build scripts or user/system build tool configuration). I do builds on systems whose firewalls only allow connections to our maven repository and SCM server, and Dokka now makes builds fail. |
This is a major blocker in my team's adaptation of Kotlin. Our build system only builds artefacts in isolation. I can see that 8e9e768 will solve this issue. Is there any plan to release this change? |
We also stumbled into this issue quickly after adopting Kotlin. We would never have expected this plugin to connect to the internet, especially not by default. |
I can confirm this fix will be included in the upcoming release 0.9.18. |
What's the fix? I still get the same error with dokka going to the internet to get package-list. Is it just adding proxy config? |
There is a configuration option |
Thanks, I did end up getting it working (for Android) with this config. dokka {
outputFormat = 'html'
outputDirectory = "$buildDir/docs"
configuration {
externalDocumentationLink {
// We can't link to external resources for source, so disable linking and
// set a local file url for package lists.
noJdkLink = true
noStdlibLink = true
noAndroidSdkLink = true
url = new URL("https://developer.android.com/reference/")
packageListUrl = new URL("file:///${rootDir}/package-list")
}
}
} |
It would be great to disable link to java documentation, similar to
noStdlibLink
for Kotlin stdlib. Without that docs generation fails with the error like this when network is not available:The text was updated successfully, but these errors were encountered: