This message was deleted.

If you are ok with 90% match (figure made up, but definitely below 100)

are you using it on a cli script or on a Gradle task?

CLI

If it were inside Gradle he would probably just use

rootDir

😄

yeah, is it mandatory to use CLI instead of a Gradle task?

Let me dig into more details of my scenario: I am writing a library that will be verifying structure of the Kotlin project. This lib will be running as JUnit test (obviously written in Kotlin), accessing and verifying Kotlin code base inside this test. The main problem here is to get the Gradle project root dir from JUnit Test (kind of CLI as it is outside Gradle, but truly it is a Java Program). Inside test I can run

File("").absoluteFile.path

to get the "current" directory path. This provides path to a source set eg.

.../project/module/src/test

(thus the traversing up approach) After @Javi "CLI question" I am thinking that It may be better to traverse up and try to run Grade command and parse

rootDir

from command output 🤔 (which command would you recommend?) BTW1 I need to explore similar approach for Maven, but this is another story BTW2 I will provide option to manually set root dir, but it would be super convenient for devs to have a method that can simply get all of the kotlin files from the current project (Gradle project root dir)

As you are in JVM, probably better follow what I said. Use the tooling API to get information about the build.