Cedric Hippmann

> @chippmann in the example you provided, gradle is complaining about ambiguous overload use: > > ``` > build.gradle.kts:38:18: Overload resolution ambiguity: > public final fun configureGodot(sourceSets: Iterable, action: GodotSourceSet.()...

@mdvarga Good to hear. I should probably add the needed minimum version of gradle to the documentation

@mdvarga Thanks for the input! I will definitely look into this issue in more detail and rework our samples so we see such issues before hand. Also i make sure...

Auto completion is not handled by this project. That is something provided by the IDE. Probably an gradle import issue. Could you clarify which steps you've taken and what version...

Ah now i understand your issue. You mean the javadoc. That's actually a great idea. @piiertho what do you think? Probably we could generate the javadoc alongside the api classes...

I now also run frequently into this issue. Hard to impossible to reproduce and happens regardless of the changes. Not even the gdj files themselves have to change. So my...

Yeah i agree. But first I'd like to investigate a bit before applying such a workaround

We discussed this a bit and we think we cannot easily fix this issue atm. A simple try catch also does not really resolve the problem. We could mitigate it...

The lifecycle info can be found in the danger box here: https://godot-kotl.in/en/stable/user-guide/properties/#exporting-properties @MartinHaeusler was this the issue and this can be closed?

> By the way, it would be super cool if this "Godot-JVM: An Exception has occurred!" would actually print the exception as well 😅 @MartinHaeusler the exception which caused this,...