Dokka: Can't find node by signature spam

[dumptruckman]

I have a Java annotation that is imported in my class and I refer to it in the KDoc with [AnnotationName]. IntelliJ correctly links to the annotation but Dokka just spams Can't find node by signature foo.bar.AnnotationName. Additionally, the generated Javadoc does not link correctly to the annotation class.

[semoro]

May be this related @FrancoSabadini

[francos]

Yes this seems more like the issue I'm having. Thanks @semoro.

[sdeleuze]

Hey, I am adding Kotlin documentation to Spring Framework 5, and I also face this issue which pollute a lot our build logs (you can have a look by running ./gradlew dokka on https://github.com/sdeleuze/spring-framework/commit/SPR-15659.

In addition to the logs, these links don't work in the generated documentation.

The related classes are in the Dokka Kotlin compiler classpath, but not the sources (since I want only generate documentation for Kotlin specific classes and functions).

A fix before Spring 5 Framework GA would be much appreciated if that's possible.

```
Can't find node by signature org.springframework.web.reactive.function.server.RequestPredicates$POST(kotlin.String)
Can't find node by signature org.springframework.web.reactive.function.server.RouterFunctions$route(org.springframework.web.reactive.function.server.RequestPredicate, org.springframework.web.reactive.function.server.HandlerFunction((org.springframework.web.reactive.function.server.RouterFunctions.route.T)))
Can't find node by signature org.springframework.web.reactive.function.server.RequestPredicates$PUT(kotlin.String)
Can't find node by signature org.springframework.web.reactive.function.server.RouterFunctions$route(org.springframework.web.reactive.function.server.RequestPredicate, org.springframework.web.reactive.function.server.HandlerFunction((org.springframework.web.reactive.function.server.RouterFunctions.route.T)))
...

[semoro]

@sdeleuze Your case fixed in d6d320eb13a24fb8e70df0ba11effabe429f0fd4 and will be available in 0.9.16

@dumptruckman Is this annotation is part of your sources, or from a library?

[sdeleuze]

@semoro Thanks!

[ZacSweers]

Is 0.9.16 in active development? I've noticed there haven't been any commits since August

[ZacSweers]

Ah nevermind, just saw there's a dev branch :+1:

[dumptruckman]

@semoro Ah, I'm sorry, I can't recall which it was. I haven't been working on that project lately. Too busy with school.

[sdeleuze]

@semoro Could you please release Dokka 0.9.16 in order to allow us to fix this issue in time for Spring Framework 5.0.3 and Boot 2.0.0.RC1 ?

[semoro]

@sdeleuze
Are you need full 0.9.16 release or some EAP will be sufficient?

[sdeleuze]

We can't use EAP version for Spring releases, so I guess full 0.9.16 would be needed.

Unrelated side note: we are also trying to fix a regression caused by https://github.com/JetBrains/kotlin/commit/5ce514bd42a8e8cb2afac99ea20bc359a4222951 that prevent us to generate the documentation only for the Kotlin code.

[mattbdean]

@semoro An EAP would be appreciated for the rest of us experiencing this issue :)

[ZacSweers]

This is still occurring on the 0.9.16 EAPs

[semoro]

@hzsweers Please, file full form issue

[ZacSweers]

You want me to file a separate issue rather than comment on this one?

[semoro]

@hzsweers Yes

[ZacSweers]

I've made it in #269, but it's effectively a duplicate of this issue.

[sdeleuze]

It seems that this issue is fixed in 0.9.16, shouldn't this issue be closed and added to 0.9.16 milestone? Also the fact that there is this issue and #269 is confusing.

[kirill-grouchnikov]

This is still happening on 0.9.17.

[DanySK]

I confirm this is happening in 0.9.17

[atoulme]

I confirm this is still happening in 0.9.18.

[xerus2000]

I didn't have this previously, but now I'm drowning in these messages...

[pavelaizen]

I confirm this is still happening in 0.10.0

Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
null:-1:-1: Tag @see cannot be used in inline documentation.  It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method.
Can't find node by signature `android.webkit.WebView`.This is probably caused by invalid configuration of cross-module dependencies

[mrclrchtr]

This is still happening in 0.10.1

[msilva-verimatrix]

Can this ticket be reopened? I am observing the same behavior in version 0.10.1:
...
[WARNING] Can't find node by signature android.view.SurfaceHolder, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.Surface, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.AudioManager$setStreamVolume(kotlin.Int, kotlin.Int, kotlin.Int), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.SurfaceHolder, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.Surface, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.graphics.SurfaceTexture, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.graphics.SurfaceTexture$getTimestamp(), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.view.Surface, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.AudioManager$setStreamVolume(kotlin.Int, kotlin.Int, kotlin.Int), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.audiofx.EnvironmentalReverb, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.audiofx.AudioEffect$getId(), referenced at ... This is probably caused by invalid configuration of cross-module dependencies
[WARNING] Can't find node by signature android.media.MediaPlayer.OnErrorListener, referenced at ... This is probably caused by invalid configuration of cross-module dependencies
...

Thank you,

Moacir

[asarkar]

I created https://github.com/Kotlin/dokka/issues/1617. If you've this problem too, feel free to vote for it to be fixed.

[DanySK]

Why opening a duplicate of a solved bug? Dokka 1.4.x does not have this issue anymore, for me at least.

[xerus2000]

For anyone still on that version, boggled by this stuff, add this line to the configuration of your DokkaTask (Kotlin DSL, may need to be slightly adjusted for Groovy)

        logging.level = LogLevel.QUIET

See also: https://stackoverflow.com/a/39736281