![]() ![]() Which versions should your plugin support? We’ve collected some insights based on download statistics in Statistics: Product Versions in Use. IntelliJ Platform based products of recent IDE versions Specific build numbers and their corresponding release version are available via Previous Releases on the corresponding product’s download page, e.g. Usually you should omit the product ID and use only the branch number and build number, for example: Multi-part build numbers can also be used in the since-build and until-build attributes of idea-version. 256.42 in XX-162.94.11.256.42) to allow plugin developers for their IDE to specify compatibility. Plugins may specify compatibility versions more precisely IDE vendors may have build numbers that are based on a specific IntelliJ Platform version and also specify additional internal version (e.g. This gives more flexibility for third-party plugins and IDE developers. In this scheme IU-162.94 corresponds to the 2016.2 release. The branch number takes the last two digits of the year, and the R release number. Since version 2016.2 of the IntelliJ Platform, branch numbers are based on the YYYY.R IDE release version numbers. Product ID ( IC for IDEA Community, IU for IDEA Ultimate, RM for RubyMine, PY for P圜harm, etc.).The number consists of the following parts: Starting with IntelliJ IDEA 9 beta, a multi-part build number is used, such as IU-162.94. Use this reference of build number ranges to specify the correct since-build and until-build values in your plugin descriptor. Testing a Custom Language Plugin Plugins Targeting IntelliJ Platform-Based IDEs Edit page Build Number Ranges
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |