Plugins with version 999.99?

Have the same issue with Cumber for Java and Cucumber for Groovy plugins. Seems to prevent updates to actual newer versions.

EDIT: I have the issue with Intellij Ultimate 2017.2.5, build 172

Hi there,

This most likely means that these plugins are bundled with IDE and they cannot be updated separately. They will be updated together with the IDE itself.

Thanks for your answer! It was definitely a bundled plugin since I could not uninstall it from the UI.

Well, I found a way that seems to fix my problem, although it is apparently not recommended: I manually deleted the plugin from the /plugin folder in the IntelliJ install directory. Then I installed a current version of the plugin via "Install from disk...". Now it has the expected version number. (Repeat this at your own risk)

I got this idea from here: https://stackoverflow.com/questions/35649488/how-to-downgrade-kotlin-in-intellij-15

Unfortunately I cannot verify that everything works now, since I have another problem with my Cucumber dependencies.

Can you answer please: any specific reason why do YOU need to do that?

yole user in that SO answer (he is one of the top devs AFAIK) clearly states that it's not a good idea.

If you need updated plugin -- just update the IDE (considering that you have 2017.2.5 ... the 2017.3 final should be released this week or so; you can grab RC version even right now)

Well, I already updated my IDE from 2017.2.5 to 2017.2.6 today. But I couldn't even be sure if the plugin had changed in any way - since it displayed the same version number as before.
From what you're saying I understand that this is not a bug but intended behavior. I guess I understand the logic behind that but I still find it a confusing way to say sth. like "this plugin is always up-to-date".

The reason why I wanted to update it in the first place: I tried to upgrade from cucumber-java 1.2.5 to 2.1.0.
When I ran my cucumber tests, I got an error that pointed to the IntelliJ plugin and had to do with a Formatter class. I had hoped that this is a compatibility issue that would be fixed in a new version of the plugin.
I can post the exact error message in a couple of hours when I have access to my notes again. (If you are interested)

Thank you for your input!

Post it -- I will try to find an existing ticket to check if it was fixed etc. Right now it could be https://youtrack.jetbrains.com/issue/IDEA-179579 (fixed for 2017.3)

But yes -- the correct way is to upgrade the IDE. Plugin may be using some new internal API/methods that may simply not be available in your current version .. which most likely will lead to IDE crash etc (if you have upgraded plugin your way, used it for a while and it still works -- quite likely there is no breaking incompatibility).

That 999.999 version should be just for preventing this. On related note: https://youtrack.jetbrains.com/issue/IDEA-125158 and linked

I tried to update from Cucumber-java 1.2.5 to 2.1.0.
As far as I remember, this was the error message I got (and it disappeared when doing the manual 'update' of the plugin):

Exception in thread "main" cucumber.runtime.CucumberException: Couldn't load plugin class: org.jetbrains.plugins.cucumber.java.run.CucumberJvmSMFormatter. It does not implement cucumber.api.Plugin

at cucumber.runtime.formatter.PluginFactory.loadClass(PluginFactory.java:179)

at cucumber.runtime.formatter.PluginFactory.pluginClass(PluginFactory.java:166)

at cucumber.runtime.formatter.PluginFactory.getPluginClass(PluginFactory.java:223)

at cucumber.runtime.formatter.PluginFactory.isFormatterName(PluginFactory.java:201)

at cucumber.runtime.RuntimeOptions$ParsedPluginData.addPluginName(RuntimeOptions.java:471)

at cucumber.runtime.RuntimeOptions.parse(RuntimeOptions.java:157)

----

In the meantime, I reverted back to 1.2.5 so I can get my tests to run somehow.

Cheers, 
Dustin

I have read the ticket you linked to just now. I have definitely also seen the Exception mentioned there. 
I guess I'll wait for 2017.2.3 to be available before attempting to upgrade Cucumber again.

Thanks for pointing me there!