This message was deleted.

How are you importing the project in IntelliJ? If using IntelliJ builtin support for Gradle, it should Just Work™ (if using

./gradlew idea

to generate an IntelliJ project, I would say it should just work as well, but who knows…)

@Thomas Broyer I use built-in gradle

I use compileOnly too and don't have any problem (e.g. https://github.com/tbroyer/gradle-incap-helper in

processor

subproject)

everything is in compileClasspath

It can, that's exactly what I'm doing in this project: https://github.com/tbroyer/gradle-incap-helper/blob/5cfcc087997e47ddfbdeef001a3a3b247dfb31d9/processor/build.gradle.kts#L16-L20

@Thomas Broyer do you know how to avoid writing: compileOny "myDependency" testImplementation "myDependency" ? With this approach you write "myDependency" twice. Is there a way to somehow specify compileOnly+testImplementation in 1 line?

No (but you can use a version catalog –or even just a variable– to avoid repeating the coordinates and prevent them from shifting by mistake; and if you have many such dependencies, besides looking like a smell, you can define a function to help you declare them in one line –I'd probably rather use a bundle in a version catalog and thus declare all of them in 2 lines in the build script)

@Thomas Broyer https://stackoverflow.com/questions/77665121/how-to-specify-2-scopes-in-1-line-in-gradle fyi