My plugin uses a locally built maven dependency - call it dependency D. Everything compiles just fine and the different Gradle classpath entries (compileClasspath, ...) look as I would expect (having used Maven so far).
Unfortunately the plugin jar created by the buildPlugin task packages ALL the maven test dependencies of dependency D. The resulting jar is therefore way too big with 20MB where it could be much less. I have no experience with Gradle and am therefore wondering whether there is a way avoid this. Is this behaviour specific to the buildPlugin task, is there some Gradle-way to alter this? Any pointer would be much appreciated. The relevant version info can be found below - I used the latest version as found in the documentation.
// Java support
// Kotlin support
id("org.jetbrains.kotlin.jvm") version "1.3.72"
// gradle-intellij-plugin - read more: https://github.com/JetBrains/gradle-intellij-plugin
id("org.jetbrains.intellij") version "0.4.21"