Hi, I wanted to check if my plugins could be easy adapated to the split mode, once most of my customers move to 2026.1 IDEs. This led me to two blocking issues.
Some context:
- because I’m developing paid plugins, I absolutely need to declare the Marketplace dependency. Unfortunately, the marketplace and the IDE flag my plugins as incompatible. I checked in the IDE (JetBrains Gateway), and the plugin browser offered me to install very old releases of my plugins, because they did not declare the marketplace dependency.
- I also need to declare a dependency to Rider module. It’s an optional dependency (
<depends optional="true" config-file="plugin-rider.xml">com.intellij.modules.rider</depends>), but the marketplace still mention it as a source of incompatibility. - for the
langmodule, OK, I will remove it and rework my code. Meanwhile, this is weird. I’m using it for Regex text fields (I will check again if it’s still inlang), and they work perfectly when installed in the frontend. But it’s not a big deal, users won’t miss it. - for the VCS module, it was declared as a strong dependency. I will make it optional.
So:
- will the marketplace plugin be compatible with the split mode? It seems critical to me. The License Facade actually works, at least on the frontend, even if it needs more time to start (between 5 and 20s, but this is fine).
- same question for optional dependencies. They’re optional, so, why are they mentioned as incompatible with the split mode? They could simply be ignored in split mode.
Thx