Intellij idea community asking for lincense verification#
Intellij idea community asking for lincense license#

Intellij idea community asking for lincense license#

Yes, but using isLicensed() is also important to have some additional protection against hackers because IDEA license checking for a plugin can be easily disabled by removing from plugin.xml. its license expires while having IDEA already open.

Intellij idea community asking for lincense verification#

> This means that IDEA will check the license at start-up anyway and that the verification calls through isLicensed() is an additional measure to make a plugin defunct if, e.g. What do other developers think about this? In which places are you putting the license check? Even if that means some users can use the plugin without a valid license simply because they haven't closed IDEA yet. My personal opinion is that I would be OK if the plugin license is checked only once at start-up. run very often and I wouldn't like to impact the performance negatively by adding a license check there. What happens if the user loses internet-connection and the license check fails although they have a valid substription? Second, most important features of a language plugin like annotators, inspections, completion, indexing, etc. For one, I don't think calling isLicensed() inside a feature that runs often is a good idea.

I'm very hesitant to implement any of these options.

Call isLicensed() periodically every 10min and simply annoy the user with a dialog that says 'You don't have a valid license'.

Call isLicensed() during the runtime when for instance highlighting or completion is invoked.

This would limit the usability drastically but since IDEA performs a license check at startup anyway and disables my plugin if necessary, this is of course useless. CompletionProviders or Annotators/Inspections.

Use a StartupActivity to check the license and if it fails I don't register, e.g.

I'm having a hard time thinking about how I can restrict/defunct my custom language plugin without accidentally annoying users. This means that IDEA will check the license at start-up anyway and that the verification calls through isLicensed() is an additional measure to make a plugin defunct if, e.g. If the license would be removed/expired when the plugin is already loaded, it's technically impossible to unload the plugin, so it will be working until the IDE is restarted. If there is no license provided in the dialog and there is no evaluation available, the plugin will be disabled and won't be loaded at all. (!) For the release version of the IDE, the plugin license will be checked on start. The article about implementing a license check says