Hi, the IntelliJ platform plugin now includes the project name in the sandbox path configuration.
Is there an option to change this? Version 2.12 of the plugin changed the default sandbox location, and version 2.13 changed it again… I’m will have to move my sandboxed IDE configurations again, and update gradle scripts (because I per-populate some config files).
Actually, I don’t see any reason to include the project name in the sandbox path. The sandbox is already located inside the project. For example, the sandbox path now looks like C:\Projects\ij-extra-tools-pack\.intellijPlatform\sandbox\ij-extra-tools-pack\IC-2025.1.4.1. ij-extra-tools-pack appears twice.
Is there a reason for this?
Thank you
Hey! Let me quickly describe the whole sandbox situation:
< 2.12.0
Sandbox was stored in the ./build/idea-sandbox/ directory.
There were often cases that developers were providing license to enable paid IDE features or paid plugins for testing purposes. However, running the clean task dropped sandbox state, so you had to repeat everything over and over.
At this time, every submodule also had its own build directory with its own isolated per-module sandbox. Even if you didn’t use it directly, it was there for final submodule’s output artifact preparation.
2.12.0
We moved the sandbox outside of the build directory, to the .intellijPlatform/sandbox common location. This was common to all submodules, meaning all of :[submodule]:prepareSandbox tasks were writing to it. I believe you see the problem.
It was also reported by @PawelLipski with Since 2.12.0, ':test' uses an output of task '...:prepareTestSandbox' (unrelated to Spotless) · Issue #2097 · JetBrains/intellij-platform-gradle-plugin · GitHub
2.13.0
Sandboxes eventually had to be isolated from each other — using intermediate directories with names of modules they are created in.
In the above screenshot, the plugin directory belongs to the root module and all other names refer to project’s submodule.
Please let me know if you have more questions or need a hand with adjusting the Gradle setup.
I see. Thx for the clarification.
Yes, the 2.12 bug on prepareSandbox hit also myself, I was waiting to have a proper split of the plugin before digging in it, but good that can be solved just upgrading the gradle plugin.
Thanks for the fast fix.
