-
Notifications
You must be signed in to change notification settings - Fork 416
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
Exception while loading package-list from ExternalDocumentationLinkImpl #213
Comments
Try again, or maybe you are behind the corporate proxy? Then you should manually download |
Hi. I am getting this error now with 0.9.15 version. This is the full stack-trace:
The 407 error is because I am behind a corporate proxy. I already have those properties defined in the gradle.properties file (systemProp.http.proxyPort, systemProp.http.proxyUser, etc.). Is it possible that dokka could use those values? |
same problem for me :-( Could you please provide an example of your workaround? I tried the following:
But got the same problem:
It seems it doesn't care about |
FYI it seems there is a difference of behavior between Dokka 0.9.15 and 0.9.16, see https://jira.spring.io/browse/SPR-16687 for more details. @fralbo On my side |
Same problem here. The packageListUrl workaround doesn't work for me either. Is it possible to address this issue for 0.9.18? |
It could be partially fixed, by providing the ability to disable external links to java stdlib, and overriding it manually |
What about the ability to read the gradle proxy settings? |
@nithdi I've started proxy on localhost and added a few lines to my
And it makes requests to proxy correctly |
@semoro You can set authentication in gradle.properties with |
@nithdi Just checked for myself, if proxy-auth enabled, it will use provided
|
@nithdi |
Good hint, but unfortunately it is still not working. Stacktrace:
1 error |
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 |
@nithdi Is your proxy requires basic authentication or client-side certificate? |
@nithdi Looks like I succeed with reproduction, for me same problem reproduces when |
@nithdi http://www.oracle.com/technetwork/java/javase/8u111-relnotes-3124969.html
See RFC 2617
|
I will try use "systemProp.jdk.http.auth.tunneling.disabledSchemes" with maven + proxy + basic authentication and let you know |
ah bit late. but just for your information. |
Ran into this same problem because we are behind a corporate proxy that uses MITM certificates. Tried the suggestion from this ticket and downloaded the file and added
However dokka would still attempt to go and download the file. It didn't appear to be respecting this configuration. Managed to stop it by following the suggestion from #188 and created a dokka-cache folder in our repository, downloaded and created the two listed files and added |
Now is 0.9.17 ,will 0.9.18 fix it? |
i tried to add nostdlibLink=true,and build successfully.may help you. |
When I try to use the dokka maven plugin I got an error - Exception while loading package-list from ExternalDocumentationLinkImpl(url=http://docs.oracle.com/javase/6/docs/api/, packageListUrl=http://docs.oracle.com/javase/6/docs/api/package-list). To fix it, I downloaded the package list and added it to the packageListUrl tag, but ended up getting a malformed URL exception. Not really sure what's wrong. Any help is highly appreciated. These are my versions:
dokka maven plugin:
Stacktrace:
|
for androidcreate a new dokka task and specified type
|
@semoro Any updates on when |
Which file should I add this in? |
I have the proper proxy settings set up in my global gradle properties file. This is the only plugin that ignores them so far. |
Add an option to disable this linking entirely, especially since it doesn't seem to work at all. |
Same!
|
I was used VPN in Chinese.Use Webpage browses the page of “google”、“android” has OK ,but terminal has not OK. I was tried Here is the exception detail:
FAILURE: Build failed with an exception.
1 error
1 error |
Most problems occured above was because of the proxy you use. Follow the steps below you will solve it .
then there you go ! |
tasks.withType<DokkaTask> {
noStdlibLink = true
noJdkLink = true
noAndroidSdkLink = true
} |
I got it to work using kennethshackleton's suggestion and the external documentation config So I downloaded package list, added it to my root dir as dokka {
// My config
outputFormat = 'html'
outputDirectory = "$buildDir/docs"
// The fix
externalDocumentationLink {
url = new URL("any url you want, doesn't matter")
packageListUrl = new URL("file:///${rootDir}/package-list")
}
} Then I added this task filter for Dokka tasks.named("dokka"){
noStdlibLink = true
noJdkLink = true
noAndroidSdkLink = true
} At which point it actually used my UpdateIn Dokka 0.10.0 the tasks filter no longer works and you'll need to remove it. Instead you add everything to your configuration: dokka {
outputFormat = 'html'
outputDirectory = "$buildDir/docs"
configuration {
externalDocumentationLink {
noJdkLink = true
noStdlibLink = true
noAndroidSdkLink = true
url = new URL("https://whatever")
packageListUrl = new URL("file:///${rootDir}/package-list")
}
}
} |
This issue is about an external location provider from old dokka. External location provider from the new dokka is sharing no code with the old one so the issue is no longer relevant. |
at org.jetbrains.dokka.ExternalDocumentationLinkResolver.(ExternalDocumentationLinkResolver.kt:25)
at org.jetbrains.dokka.ExternalDocumentationLinkResolver.class(ExternalDocumentationLinkResolver.kt:25)
while locating org.jetbrains.dokka.ExternalDocumentationLinkResolver
for parameter 4 at org.jetbrains.dokka.DeclarationLinkResolver.(DeclarationLinkResolver.kt:9)
while locating org.jetbrains.dokka.DeclarationLinkResolver
for parameter 0 at org.jetbrains.dokka.PackageDocs.(PackageDocs.kt:13)
at org.jetbrains.dokka.PackageDocs.class(PackageDocs.kt:12)
while locating org.jetbrains.dokka.PackageDocs
1 error
This issus shown when i use ./gradlew dokka
how can i fix this.
The text was updated successfully, but these errors were encountered: