Not seeing how to enable a plugin only for a certain project

I noticed that all of my plugins are enabled for all projects even if they're not needed or compatible. This has been a problem before, because a plugin has crashed the whole editor on a project that had no use for the plugin.

I'm not seeing how to only enable a plugin for a certain project.

3 comments
Comment actions Permalink

The feature is not there yet: https://youtrack.jetbrains.com/issue/IDEA-230227
They've tried to integrate it into one of the past releases and it's caused dramatic performance regression. There's no ETA on when it's going to get done, unfortunately.

0
Comment actions Permalink

Reading that ticket indicates the plugins feature or something they rely on is poorly-architected. I'm surprised considering PHPStorm is based on Java, which I've never heard of this issue with when it comes to package inclusion (which I'd think plugins would work the same way as). I'm scratching my head on this one, but who's to say whether the restriction is based on Java or JetBrains having some sort of weird architectural design issue, or operating systems having some sort of weird limitation somewhere?

 

0
Comment actions Permalink

It's a restriction of our indexes implementation, somehow, despite them not being shared among different projects (AFAIU), they are tied together, and, for instance, there's no way to invalidate indexes for a certain project only.

0

Please sign in to leave a comment.