Hi I just finished implementing a feature with LSP4ij But I am thinking of splitting the plugin so that I will release 1 version with this implementation targeting noncommercial IDE and implementing using the Jetbrains SLP infrastructure targeting commercial IDE. Any suggestion on how to do it? Should I create subprojects for each implementation or any other suggested approach? I went over the documentation but not sure about the solution. Thanks

Hey Jonathan! LSP4IJ is open source product with lots of supported LSP specification features (methods). Last time I touched JB LSP there were ~10 from more that 100 from the specification. It’s all depends on LSP4IJ license, but I’d did all in combination and with freemium subscription: some features are free all the time, some features paid with or withoud trial period. If you’re able to implement the missing features from JB LSP, then go on with JB LSP because it’s convenient to use compared with LSP4IJ

Hi @xepozz Thanks for the reply. My plugn’s lsp feature requirements are small and is not a matter of features but I am thinking more from the user perspective that in non commercial IDE they will also have to install the lsp4ij plugin, and since I don’t want to make it mandatory of they don’t the lsp support is disabled. Since the majority of the plugin users are Rider and Ultimate the Jetbrains lsp support will be available if I use that… So this is why, I though on splitting the plugin into two…

I may wrong, but I thought if a user install a plugin, all dependencies will be installed automatically, right?

You can mark a dependency optional

So in this case the best way is to split the plugin: the one with required LSP4IJ and the other is about JB LSP integration

To speak from my own experience: publishing two similar plugins will not only take considerably more maintenance efforts but also cause much confusion for users. It is possible to allow choosing between the two clients (I’m doing exactly that) with LSP4IJ being optional. But there’s a catch: The two clients cannot be both loaded in the same session. Most users will use the default settings, so it’s very unlikely this bug will be encountered by the average user. Thus, I think the best possible solution is to: Make LSP4IJ an optional dependency If the native client is available, use that. Otherwise, notify the user that they need to install LSP4IJ and provide them a convenient way to do so (a notification action in the form of a button?). Disclaimer: I never tried this approach, since in my case I have a third, “command line” mode as the default.

Thanks, @insyncwithfoo - yes having two similar plugins sounds complicated. @yann.cebron @jakub.chrzanowski - is there an internal discussion at JetBrains to open LSP to all IDEs? any suggestions from your experience?

I can only recommend sticking to our API as we are sure it is much more performant and battle-tested than anything else. No plans to port it to Community edition so far. At the same time you may consult to your own plugin statistics about IDE usages and spot some patterns in paying users choices.

See also Update on LSP and Template Language APIs in PyCharm

Please note the update on IntelliJ IDEA [image] LSP API available in IntelliJ IDEA Ultimate 2025.2 without paid subscription Announcements Starting with version 2025.2, the LSP API will be fully available in IntelliJ IDEA Ultimate, regardless of whether a user has a paid license or no license at all. See the blog post: IntelliJ IDEA Moves to the Unified Distribution If your subscription expires, you won’t be locked out of the IDE. Instead, you will continue to have access to the full IDE, but with the feature set matching what is available for free (previously known as Community Edition). and also: But even without a subscri…

LSP Targeting multi product

IntelliJ Platform

yuriy.artamonov (Yuriy Artamonov) July 18, 2025, 8:57am 13

Please note the update on IntelliJ IDEA

Topic		Replies	Views
LSP API available in IntelliJ IDEA Ultimate 2025.2 without paid subscription Announcements lsp-api , lsp	20	1243	September 4, 2025
New LSP Client Implementation Showcase & Feedback	8	476	September 21, 2026
Update on LSP and Template Language APIs in PyCharm Announcements api	4	969	April 23, 2025
Is there a special place where plugin can store binaries that are shared between different IDEs? IntelliJ Platform plugin-development	1	183	July 1, 2025
Open-Sourcing the LSP Client API Announcements lsp-api , blog , api	0	103	June 26, 2026

LSP Targeting multi product

Related topics