Hello folks! Is there any problem with `gradle-com...

# gradle

[x80486]

Hello folks! Is there any problem with gradle-completion and Kotlin DSL Gradle scripts? I see it doesn't quite "discover" (read: auto-completes) all the tasks correctly...

[gildor]

Tasks? I'm not sure that there is task completion, it's dynamic API, there is an issue about generation of task accessors

[x80486]

The available tasks you can run as part of `./gradlew ...`; there is only a sub-set of them that appear using Kotlin DSL. When using Groovy everything is fine. Not sure if that's an issue or it's mean to be like that. I noticed that clean, assemble, etc. cannot be auto-completed – not discovered, doesn't appear, etc.

On every project that I have (that uses Kotlin DSL), these are the only tasks (maybe they are called something else, that's the name I know) appear, like all the time:

[gorre@uplink kotlin-vertx3]$ ./gradlew 
buildEnvironment     - Displays all buildscript dependencies declared in root project.
components           - Displays the components produced by root project.
dependencies         - Displays all dependencies declared in root project.
dependencyInsight    - Displays the insight into a specific dependency in root project.
dependentComponents  - Displays the dependent components of components in root project.
help                 - Displays a help message.
init                 - Initializes a new Gradle build.
model                - Displays the configuration model of root project.
projects             - Displays the sub-projects of root project.
properties           - Displays the properties of root project.
tasks                - Displays the tasks runnable from root project.
wrapper              - Generates Gradle wrapper files.

[gildor]

Ohhh, you are talking about task completion on CLI gradle.
I don't think that completion somehow different with kotlin-dsl, pretty sure it's the same in groovy

[gildor]

Anyway, if you sure, you can fill an issue on gradle-completion GitHub
Also, try to check autocomplete with full module path, Gradle completion doesn't show tasks inherited from subprojects by default, only tasks for current project

[x80486]

That's what I thought: it shouldn't be different. It could be something in my desktop's setup (one never knows), but it is weird that it works with all my Gradle-Groovy projects and only the tasks that I sent before appears on Kotlin DSL ones

[x80486]

I'll file an issue, and let's see how it goes! 👍

[gildor]

Did you try autocomplete with module path? Like ./gradlew :someModule:clean