![]() To use this in your plugin you should add a new parameter optional to product-descriptor in your plugin.xml file. You can find more information about supported scenarios and discussion about this feature’s implementation in the relevant issue. We’ve had quite a lot of requests to provide an option to disable the forced licensing check on plugin start so that it would be possible to implement free and paid functionality in the same plugin and trigger the license dialog only for paid functionality. With Custom Pages, you can turn your plugin page into a full-featured website with all the information you want to provide:įree functionality in paid plugins implementation We’ve been testing this functionality with paid plugin vendors for quite some time, and we are thankful for all the feedback you gave us! Starting this week, custom content pages functionality is available to all plugin vendors. The new sales page provides you with more insights into your customers’ purchases, shows you more granular statistics, and lets you export data for further analysis. It is useful for checking licenses in your own systems, in advanced support workflows, and for troubleshooting licensing issues.Ĭheck out more information about this API in our documentation. With this simple API, all paid plugin vendors can check whether a user with a specified email address has a license. This option was announced at the launch of the Marketplace, but it took us around half a year to sign all the necessary agreements with our partners. JetBrains is utilizing its reseller and distributor network to make plugins available via our established distribution network, which is crucial for some markets where direct sales are problematic. To celebrate the anniversary of Marketplace paid plugins, this week we launched Special Offers and Coupons Self-Service for paid plugin vendors, which lets you create offers and discount coupons on your own. When downloading a paid plugin, a special plugin that implements the licensing functionality will be installed as well. License support works out of the box in all community editions of IntelliJ-based IDEs, including third-party IDEs, and it is available starting with version 2019.3.1 for JetBrains IDEs (more precisely, IntelliJ IDEA build 193.5662.53 and later builds). ![]() This includes IntelliJ IDEA Community Edition, P圜harm Community Edition, IntelliJ IDEA Edu, P圜harm Edu, MPS, and all the third-party IDEs built on top of the IntelliJ Platform, such as Android Studio. Realizing this drawback, we started working on a solution right away.Īt the very end of 2019, we extended the market for plugin vendors by making paid plugins also available in the community editions of IntelliJ-based IDEs. We are very proud to work with all our vendors of both free and paid plugins, and today we want to highlight some of the major updates we’ve made to paid plugin functionality on the Marketplace and in our IDEs during the first year of the Marketplace’s operation.Īt launch, we supported paid plugins on Marketplace only for commercial editions of our IDEs, because the Community Editions lacked any kind of licensing mechanisms. We have 46 paid plugins published as of today, and dozens of paid plugins in the pipeline at different stages of development, testing, and release preparation. Since then, we have been continuously bringing more and more paid plugins to the Marketplace. We started this journey with 10 paid plugins for IntelliJ IDEA–based IDEs on that day, with all sales and support carried out via JetBrains sales infrastructure. ![]() Just over a year ago, on June 26, 2019, we announced the launch of paid plugins on the JetBrains Marketplace. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |