IntelliJ plugin shows "Plugin is incompatible with the installation"

Answered

Hello All,

I am creating intelliJ plugin and using gradle build to create zip file . I have given 

intellij {
version '2017.3.3'
}

and the plugin was working for  2017 version.

When I installed 2018.1 the plugin is showing incompatible version. So I changed version in gradle it to 

intellij {
version '2018.1.2'
}

Now it is only working in 2018.* intelliJ , not in 2017. I manually given below in plugin.xml. but it is getting overwritten by gradle build.

<idea-version since-build="173.*" until-build="181.*"/>

 

So, Do we need create separate plugin zip file for each major versions ?  Please advise.

Thanks in advance

Manoj K Nair

0
7 comments
Avatar
Yaroslav Bedrov

Hello,

You can disable this feature by setting the "intellij.updateSinceUntilBuild" option to "false": https://www.jetbrains.org/intellij/sdk/docs/tutorials/build_system/deployment.html

1
Avatar
Permanently deleted user

Thanks ! It helps !

0
Avatar
Yaroslav Bedrov

You are welcome!

0
Avatar
Permanently deleted user

Hi, I am trying to add the following plugin to Intellij but I am giving ''Plugin 'Galen Specs Language Support' is incompatible with the installation" error. Can you help me, please?

https://plugins.jetbrains.com/plugin/8302-galen-specs-language-support/update/33143

My Intellij info:
IntelliJ IDEA 2019.3.1 (Ultimate Edition)
Build #IU-193.5662.53, built on December 18, 2019

0

@...

Plugin's author has updated the plugin in 2017, So, the plugin is incompatible with IntelliJ IDEA 2019.3.*. You can see that on plugin's page: 

0
Avatar
Permanently deleted user

Konstantin Annikov 
hi,  is there any way to update files like plugin.xml to fix this problem locally? Regardless thanks a lot.

0

You can download the plugin at this page: 

https://plugins.jetbrains.com/plugin/8302-galen-specs-language-support/versions

Unpack the archive and make necessary changes in the plugin.xml file. But the chance that plugin will work as expected is very low. 

So, please note that you are doing that on your own risk and this way is not supported. 

0

Please sign in to leave a comment.