@isNotOkay Please ignore the ‘com.intellij.modules.json’ in the Plugin Verifier results. This is a known false positive, which is under top priority issues currently being fixed. Sorry for the inconvenience.
1 Like
This means when I release a new version my plugin should get approved by the team even when the plugin verifier states that this problem exists for 2025.1?
though this is a known issue, it blocks the publishing of plugin, any upate?
I solved it as follows: I declare the dependency as optional in plugin.xml, I specify an empty json.xml
<!-- plugin.xml -->
<depends config-file="json.xml" optional="true">com.intellij.modules.json</depends>
<!-- json.xml -->
<idea-plugin require-restart="false">
<extensions defaultExtensionNs="com.intellij">
</extensions>
</idea-plugin>
but I do not declare com.intellij.modules.json in bundledPlugins() bundledPlugins(“com.intellij.modules.json”)
@eltonsandre This is incorrect, you will have failures at runtime. In your main plugin classloader there will be no access to JSON classes anymore
I don’t want to create confusion about this issue. 
Yes, if the user disables/uninstalls the JSON plugin, this will indeed be a problem for versions after 243.+.
In this scenario, perhaps the correct approach would be to move the JSON language-related features to the json.xml file, keep it as mandatory, and coexist with the other features that do not depend on the JSON plugin.
However, in practice, this is the strategy I have been using as a workaround since versions 243.+ to solve the verifyPlugin issue, and it has worked for me. I have no reports of ClassLoader related issues, and I have supported versions SinceBuild=231 to UntilBuild=251.+.
I currently use the plugins that fit this scenario and have no bugs related to ClassLoader.
Please note that the JSON plugin must be installed and enabled for versions 243 and higher.
//TODO I am working on moving the JSON resources and generating a SinceBuild=243 version.
I’m really speechless. This is a known issue that has been preventing me from releasing my plug-in for a month, and I still haven’t received any news. It’s really frustrating.
I got mine approved after sending an email. See:
2 Likes
I’m sorry but this is going beyond ridiculous… it’s been a month without a fix and the solution is searching in some chat for an obscure message saying to send an email to skip approval??
Meanwhile I’m (we’re?) getting automated emails every few days saying that the plugin is not yet approved because of compatibility issues.
By the way, we had the exact same problem in the previous major releases, that somehow got solved, and now somehow the issue reappeared.
On top of the catastrophic mess that is gradle, this is the reason I’m not bothering with contributing to the IDE. It’s just not feasible to spend HOURS trying to get code that USED TO WORK, to build again, with the only change being just a change in the “until version” setting.
4 Likes