chore(jetbrains): migrate to stable IntelliJ Gradle plugin - #11869
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge The only change since the last review is a one-line documentation addition to Files Reviewed (1 file changed since last review)
Previous Review Summary (commit 1285e54)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 1285e54)Status: 1 Issue Found | Recommendation: Merge Overview
Issue Details (click to expand)SUGGESTION
Files Reviewed (10 files)
The Reviewed by claude-sonnet-5-20260630 · Input: 16 · Output: 2.9K · Cached: 357.7K Review guidance: REVIEW.md from base branch |
chore(jetbrains): migrate to stable IntelliJ Gradle plugin
What
kilo.splitModeServerPort=0, and wire:runIdeSplitModewith the same local CLI prep as backend runs.:runIdeSplitModeGradle config and refresh developer docs.Why
This catches our JetBrains plugin development tooling up with the now-released IntelliJ Platform Gradle Plugin work from JetBrains/intellij-platform-gradle-plugin#2164. With 2.17.0 released, we can stop carrying the local random-port workaround and snapshot repository setup.
Notes
--no-configuration-cachebecause the IntelliJ run-IDE tasks still hit a configuration-cache serialization issue in this setup.Validation
./gradlew tasks --all./gradlew typecheck./gradlew --no-configuration-cache runIdeSplitMode --dry-run -Pkilo.splitModeServerPort=0 -Pkilo.dev.storage.isolated=truebun turbo typecheck(pre-push)