![]() ![]() Thanks for the alternativeIdePath suggestion - I was just using the adle file from the wizard as described in, and there were no issues when running the plugin in the sandbox (using the `runIde` gradle task). ![]() on `master` branch we use `intellij.version = 2018.1.3` and on 173 branch we use `intellij.version = 2017.3.5`, and publish all of them. Usually, we build different plugins against different IDE version. > If so, I'd appreciate any advice you might have as how to handle supporting backwards and forwards compatibility for that use case. We're trying to make changes backward-compatible, so plugin built for 173 branch will work on 181-branch runtime (sometimes we fail though: ).īut we're not really trying to keep forward compatibility and allow plugins built against 2018.1 run on 2017.3. > Is the reason that with a newer version of IDEA, you might be using backward-incompatible APIs when testing? You can use IntelliJ 2017.3 for compiling, It will match Android Studio sources more but not entirely too. If they were, you didn't get the compatibility error :) Android Studio usually is based on an old IntelliJ branch. > I'm using IDEA to develop a plugin for use in both Android Studio and IDEA and they tend to be quite out of synch. The compiler won't say you about a missing class or method (because they present in 181) that you used but you'll get an exception on runtime in Android Studio. There are plenty of changes between them, including changes in API. You use IDEA 2018.3.1 (181 branch) for compiling and run the plugin on Android Studio 3.1.2 (173 branch). I've spent hours on trying to figure out what is making this not work. It would be great if the IDE could state *what* is making the plugin incompatible with the installation (e.g., "Required build range X-Y, installation is Z"). I've also tried uncommenting the depends sections and adding an until-version. I've tried using the following since-versions: I'm getting this same error, with the following plugin.xml: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |