This message was deleted.

I've seen seldomly that the up-to-date state got confused and didn't rerun tasks with changed inputs. I was not able to investigate what causes it or how to targetly fix it. I just tried to get the colleague back on track quickly. So delete

.gradle

in the root project and everything in

<GRADLE_USER_HOME>

except things you created manually like

init.d

directory or

gradle.properties

. Then the up-to-date checks should hopefully work properly again if it is the same issue I've observed occasionally.

Hello, I had similar behaviour in intellij when I was switching between delegating building to gradle and using intellij compiler. Intellij compiler produced class files into

out

folder which idea picked up even when it was already switched to delegate to gradle and was causing picking old compiled classes to be loaded first on the classpath. Solution was deleting the

out

dirs in modules

What I described was a pure Gradle problem though, building from the commandline. But what you describe sounds like a bug you should report at youtrack.jetbrains.com if you didn't already. :-)