Victor Saar

Created June 05, 2018 09:11

Hi Daniil, yes, you're right. I already figured that myself in the meantime. I was building and running tests for my plugin on a CI server, which was compiling the source for each supported version...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Change to QueryExecutor and RequestResultProcessor interface is not backwards compatible

• 0 votes

Created May 18, 2018 20:23

AFAICS, the easiest way to make it backwards compatible would be to rename the affected methods. That way consumers of the API could simply implement the new method and leave the old one as is.

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Change to QueryExecutor and RequestResultProcessor interface is not backwards compatible

• 0 votes

Edited January 24, 2018 14:54

There's an attribute called "optional" that does exactly what you want. In that case, the extensions specified in "other_plugin.xml" will only be registered when users of your plugin have the depen...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Using another plugin only when it is installed

• 0 votes