MartinHaeusler
commented
8 months ago New insight: The idea plugin itself only seems to operate as a top-level plugin.
For instance, if I do this in a sub-project:
plugins {
idea
}
println(idea.project)... it prints null (which explains the NullPointerException).
If I do the same thing in the top-level project, I get:
org.gradle.plugins.ide.idea.model.IdeaProject_Decorated@100fc7c0
This is consistent with my other observations and explains the NullPointerException. The questions that remain are:
- is this a bug in the idea plugin or is this intentional?
- if it is indeed intentional, how do we work around it?
Frontrider
chippmann
My build setup is a fairly standard multi-module build and looks as follows:
The root
build.gradle.ktslooks like this:... and the client
build.gradle.ktslooks like this:The other
build.gradle.ktsfiles are empty. Thesettings.gradle.ktslooks like this:From my point of view, this should work. Sadly, I get a
NullPointerExceptionwhen I attempt to run even basic gradle tasks (such as./gradlew projects):Aside from all the noise, the last part is interesting:
I've had a quick look into the source code of the godot gradle plugin. It seems to attempt some sort of interaction with then IntelliJ IDEA plugin. I tried adding that plugin, but unfortunately it changed nothing.
Using the gradle plugin in a standalone setup (i.e. without sub-modules) it works just fine, but it doesn't seem to play nice with multi-module builds.