No, it would not until number of usages changes / new files with errors appear, we will still approve it. You may have noticed Ignored Internal API usages group in your plugin check results
Ah, good to know. I didn’t notice.
I suppose it’s different to local plugin verifier results, which don’t have that history.
There’s one more use-case I noticed, hopefully that’s covered by the provided read-only data.
I’m using the descriptor to detect if a given module is enabled.
I’m using it in Noctule to control if a FileTypeOverrider is enabled and to add a suffix to the displayName of my Language if another, known language is already made available with the same display name.
private fun PluginDescriptor.isProvidingModule(moduleId: String): Boolean {
if (this !is IdeaPluginDescriptor) return false;
return contentModules.any { moduleDescriptor ->
moduleDescriptor.contentModuleName == moduleId
}
}
A quick question, my plugin compatible since 2024.1, is it ok to just depend on com.intellij.marketplace in plugin.xml ?
I am afraid this is available only since 2025.1.
For your information, 2024.1 is unsupported version for us, we do not even issue security patches for versions older than 3 Major versions back
Some third-party IDEs are still based on older versions of IntelliJ, such as Huawei DevEco Studio, which is significantly late and, in my opinion, it has been altered too much by Huawei (activating a license is painful). So I would say this is the problem of Huawei.
Given the marketplace plugin:
- when targeting 2025.1+ IDEs, you can simply add the marketplace dependency in your plugin.xml. The IDE will install it if needed. This is a big improvement
. If malicious users unsinstall the marketplace plugin and edit your plugin.xml, you will simply get a null Licence Facade. I personally wait ~four minutes before checking the License Facade, which is clearly enough for the License Facade to start. - when targeting older IDEs, there are two situations:
- community IDEs: they don’t have the marketplace plugin. In this case, you have to add the marketplace dependency. Unfortunately, in some rare cases, users still have to download the marketplace plugin manually from the website, and they have to pick the exact compatible build.
- ultimate (paid) IDEs: the marketplace plugin is already integrated into the IDE. You must NOT depend on the marketplace plugin. i.e. don’t add
<depends>com.intellij.marketplace</depends>, otherwise the IDE will may it cannot find the marketplace plugin.
I supported both IntelliJ community and ultimate 2024.1+ (actually 2023.3+) IDEs, + Android Studio and DevEco Studio, by publishing three distinct builds:
- old community IDEs: with
<depends>com.intellij.marketplace</depends>and<idea-version since-build="233" until-build="243.*" />. Example - old ultimate IDEs: without
<depends>com.intellij.marketplace</depends>, but I also added<depends>com.intellij.modules.ultimate</depends>to make it incompatible with community IDEs. And<idea-version since-build="233" until-build="243.*" />. Example - 2025.1 IDEs:
<depends>com.intellij.marketplace</depends>and<idea-version since-build="251" />
I did this some time just for DevEco Studio, because it was based on 2023 and 2024 IDEs. If my memory is correct, it just moved to 2025, and future builds may be based on 2026, but we can’t download beta builds outside from China.
I also stopped testing my plugins with DevEco Studio, as I have only 2 users 
(and they don’t pay…). DevEco has a whitelist of plugins, but it’s like they’re only free and freemium and I can’t apply to it (I wasted so much time with their support team, they’re just too bad). But this is another story. I just want to say: don’t expect too much from DevEco Studio and Huawei. In most cases, you should focus on JetBrains IDEs and Android Studio, and support only 2025.1+ IDEs.
Woops, yes, you’re absolutely right. Devco Studio 6 was supposed to be based on IJ 2025 (unofficial sources…), not 2026. So, it’s still based on 2024? That sucks