runPluginVerifier no longer works for plugins with "intellij" in plugin ID
已回答
As per this post, existing plugins can contain “intellij” in pluing ID. However, plugin verifier stopped working for these plugins.
First, I get this warning (ok, I can live with this):
> Task :verifyPlugin
[gradle-intellij-plugin :verifyPlugin] Invalid plugin descriptor 'plugin.xml'. The plugin id should not contain the word 'intellij'.
But then, after plugin verifier runs, I get:
Scheduled verifications (0):
The following files specified for the verification are not valid plugins:
X:\path\to\plugin\project\build\distributions\my-plugin-1.0.0.zip
The plugin descriptor 'plugin.xml' is not found.
And no verification result or report is produced.
My other plugin (new one, without “intellij” in plugin ID) works just fine.
请先登录再写评论。
Hello Slawomir,
Plugin Verifier 1.364 has a known issue with plugin descriptor discovery. This is not connected with `intellij` in plugin ID.
Please track the corresponding YouTrack issue.
https://youtrack.jetbrains.com/issue/MP-6388
Sorry for the inconvenience.
The issue MP-6388 (and therefore the error about 'plugin.xml' is not found) has been fixed with version 1.365, but
:runPluginVerifier
still fails for such plugins when usingFailureLevel.ALL
.This is the error message:
Noticeably, the Plugin Verifier will not generate a report, which is confusing. However, we can see the following in the Gradle log:
It also looks like the actual verification against different IDEs is completely skipped. Before starting with the actual verification against various IDEs, it looks like the plugin verifier removes the plugin from the list of plugins which shall be verified because it is not considered a (valid) plugin.
By removing
FailureLevel.INVALID_PLUGIN
from the failure levels (or by using the default failure levels), the Gradle task runs through again, but the actual verification of the plugin is still skipped.I am also not sure which other failures would be reported as
FailureLevel.INVALID_PLUGIN
, as the failure type already existed before. So I am not sure if ignoring this type of failure is a good solution in general.The issue still occurs.
First, I get this message:
The plugin verifier version is 1.365:
Then verifier fails because the “plugin is invalid”:
No verification report is produced.
It can't be related to https://youtrack.jetbrains.com/issue/MP-6388, as this issue is already fixed.
See also: https://github.com/sczerwinski/wavefront-obj-intellij-plugin/actions/runs/9055484213/job/24876856021?pr=597#step:7:311
Since then, multiple issues have been fixed in the Plugin Verifier.
Let me point you to the -mute command-line option that allows to suppress specific plugin problems that are not actionable by the existing plugins. This might apply to the The plugin id should not contain the word ‘intellij’ kind of issues.