Hi, I just noticed that Dataspell 2025.3 is marked as incompatible with the Marketplace plugin. I think it should not.
Adding the Marketplace dependency works with most 2025 IDEs, as we’re supposed to do that to ensure users can register our paid plugins (I followed JetBrains advice). Without this dependency, users may not have the Marketplace plugin, and they wouldn’t be able to activate their license (this is the case for Android Studio. Some Rider users reported similar issues).
So, it works with most 2025 IDEs, except for Dataspell.
I tried to install my paid plugins manually (install plugins from disk) in Dataspell 2025.3 and everything works fine. I can activate my licenses, even if I don’t see the Marketplace plugin in the list of bundled/downloaded plugins, so I guess Dataspell is like older IDEs: the code that manages license registration is already included in the IDE.
Unfortunately, I can’t install my paid plugins from the plugin browser because Dataspell is market as incompatible with the Marketplace plugin.
One last thing: I see the recent releases of the Marketplace plugin are now compatible with a reduced set of IDEs. I’m lost.
My understanding was that:
IJ Ult 2024 and all the other paid IDEs did not need the Marketplace plugin because the code that manages license registration is already included in the IDE. Solution: depend on the com.intellij.modules.ultimate module (all paid IDEs have this module), and absolutely NOT on com.intellij.marketplace.
IJ Community 2024 and all the other free IDEs needed the Marketplace plugin. Solution: depend on the com.intellij.marketplace plugin.
This forced us to maintain two branches, but it worked.
In theory, all 2025 IDEs (paid an free) are supposed to need the Marketplace plugin because they’re unified IDEs. At least, this is my understanding. Problem:
Does it means GoLand, DataGrip, PhpStorm, Rider etc will be incompatible with the Marketplace plugin? What should we do if we want to be sure our customers can activate their license? As you can see, I think I can’t simply play with the com.intellij.modules.ultimate and com.intellij.marketplace dependencies as with 2024 IDEs.
So seems the safety way to check IDE marketplace dependcy is still use depends “com.intellij.modules.ultimate”, or incompatible-with “com.intellij.modules.ultimate” and depends “com.intellij.marketplace”
I think recent releases of the Marketplace plugin are simply not configured correctly. Same thing for Dataspell.
Otherwise, it will be a nightmare because, I think, CLion DataGrip Dataspell etc depend on com.intellij.modules.ultimate, so, we won’t be able to say they depend on marketplace + they’re incompatible with ultimate. Our 2024 dependency matrix won’t work for 2025 IDEs.
Since this year com.intellij.marketplace plugin alias exist in all commercial IDEs as well even without a plugin itself. So one can depend on it regardless of community or Android Studio builds. If the IDE misses this built-in then it installs the required plugin by dependency. We use this mechanic for AI Assistant and Junie plugins
There might be a problem with mapping of modules for DataSpell on the Marketplace backend side, probably when we compute plugins we do not see DataSpell has this plugin alias included to build.
FYI I test install from disk in DataSpell 2025.3 seems work fine, while install from plugin manager seems work incorrect. So maybe this is a issue caused by marketplace side not IDE side.
Dataspell is still marked as incompatible, but if you click on it, there’s nothing (and the little arrow is missing).
Also, try to find “Extra Tools Pack” via Dataspell’s plugin manager, it won’t find it.
IDEs contain plugins physically or declare supported modules with names (plugin alias) in their plugin.xml. If there is no module name in build - plugin considered incompatible with IDE, cannot be installed with missing dependencies.
