Describe the bug
When using version 5.2.5 of com.jfrog.artifactory when debugging from IntelliJ gradle can never reuse its configuration cache because
Calculating task graph as configuration cache cannot be reused because system property 'idea.debugger.dispatch.port' has changed.
Changing 'idea.debugger.dispatch.port' on every run in and of itself would be ok, but build-info-extractor-gradle-5.2.5.jar!\initscripttemplate.gradle captures the whole of gradle.startParameter.getProjectProperties(). I've also opened a bug in IntelliJ, please work together to decide on who fixes what, I'm just a user ;)
Describe the bug When using version 5.2.5 of com.jfrog.artifactory when debugging from IntelliJ gradle can never reuse its configuration cache because
Calculating task graph as configuration cache cannot be reused because system property 'idea.debugger.dispatch.port' has changed.
Changing'idea.debugger.dispatch.port'
on every run in and of itself would be ok, butbuild-info-extractor-gradle-5.2.5.jar!\initscripttemplate.gradle
captures the whole ofgradle.startParameter.getProjectProperties()
. I've also opened a bug in IntelliJ, please work together to decide on who fixes what, I'm just a user ;)https://youtrack.jetbrains.com/issue/IDEA-363515/Gradle-configuration-cache-never-reused
To Reproduce I've attached a sample project. Debug the task
:app:launch
to reproduce.Expected behavior Gradle can always reuse the configuration cache.
Screenshots See ticket in IntelliJ
Versions
Additional context testproject-configcache.zip