With a gradle project without modules (build.gradle.kts and settings.gradle.kts at root), is there any reason the java{} and sourcesSets{} and dependencies DSL would be highlighted red? Most gradle projects have submodules, but this one does not because it's a mixed kotlin/groovy project 😞

That's not exactly "without modules", but "without subprojects" 😄 Only reason should be, that the project is not synced, press the sync button in the Gradle toolwindow and wait a bit. Btw. why don't you use the accessor for the Groovy plugin too? Looks a bit inconsistent that way. 😄

ok...technically, it's without subprojects (but most people think of them as modules) I should have mentioned I did all the usual incantations (sync, invalidate caches, etc.) 😂 lol..I can switch to use the groovy accessor too. Same result though 😞 I wish there were logs on "why is this stuff red" 😛

> most people think of them as modules > Not the people I know. :-D Mostly people just still trapped by Maven terminology, but imho one should adapt to the terminology if the tool one is using. :-) Besides that this was not even what I meant. I could also have said "without submodules", not "without modules" as the root project is not in any way special, I just shifted to the proper terminology at the same time. :-D > I should have mentioned I did all the usual incantations (sync, invalidate caches, etc.) 😂 > > I wish there were logs on "why is this stuff red" 😛 > It does build though, right? If you build from commandline for example.

When I'm writing gradle plugins, I think in terms of subprojects, but non-gradle folk think of these as modules in some of our projects 😂 yep, ./gradlew check assemble works fine also have done the close/reopen before..I think this is some weird IntelliJ thing...I'll ask the jetbrains folks...thanks!

Mostly people just still trapped by Maven terminology,

To be fair, project being the entire repository and module being a subdirectory is also the terminology of IntelliJ.