I see some issues (like 2.4.0 Configuration takes 25s vs 2s with 2.1.0 · Issue #1905 · JetBrains/intellij-platform-gradle-plugin · GitHub) depends on (and are affected by?) the Plugin Verifier.
I’m just wondering if I can disable the Plugin Verifier completely. I don’t use it locally. I check the online report generated by the marketplace.
Thanks.
Tool |
Version |
Gradle |
8.13 |
IntelliJ Platform Gradle Plugin |
2.1.0 and 2.4.0 |
Would something like below work for you?
tasks {
verifyPlugin {
enabled = false
}
}
Unfortunately, verifyPlugin
is deprecated. I’m trying to find something similar in pluginVerification
, but the code completion in build.gradle.kts
is a bit broken (again…) in IJ
.
@jonathanlermitage.1 Disabling Plugin Verifier won’t help mitigate the linked issue.
Plugin Verifier exists in two forms:
- as a CLI tool, which is executed when running the
verifyPlugin
task
- as libraries that handle some logic related to IDE layout, plugins dependencies, and classpath calculation – those libraries are used in multiple places across the Gradle plugin
To fix the performance problems, Plugin Verifier has to adjust how it handles IntelliJ Platform jars, relations, and FS operations.
I see. Thanks for the clarification.