How to bundle modules intellij.platform.collaborationTools.auth.base and intellij.platform.collaborationTools.auth?

IntelliJ Platform
1

I’m running into exceptions at runtime on 2025.3, I think it’s related to these notes:

Several modules were extracted from the core plugin to separate modules with their own classloaders. This shouldn’t affect binary compatibility, but an explicit dependency should be added in build.gradle.kts using bundledModule(<moduleName>) if a plugin uses API from these modules:

  • intellij.platform.collaborationTools.auth.base

  • intellij.platform.collaborationTools.auth

I’m trying to add these as bundled modules like so:

bundledModule("intellij.platform.collaborationTools")
bundledModule("intellij.platform.collaborationTools.auth.base")
bundledModule("intellij.platform.collaborationTools.auth")

Doing this gives me an error on Gradle:

Specified bundledModule ‘intellij.platform.collaborationTools.auth.base’ doesn’t exist.

Any ideas what to do?

1 Like
4

Hi Matt,

This appears to be the same error you would get if you try to build against 25.2 and lower.

I’m trying to reproduce it in a quick test project, but I’m unable to get to a state where I have a dependency on platform 25.3.
Could you share your Gradle setup so I can try to reproduce what you’re experiencing?

5

I think this is a repro of what we are seeing: GitHub - fkorotkov/intellij-plugin-bug-reproduction

6

I think I’ve just grokked your comment. We have been setting the build against our lowest supported version of 2024.2, which is why we can’t use the new bundled modules.

What is the best practice here, should the build for our latest supported version or our oldest? If we want to support all versions, 2024.2+, do we need to build two variants of the plugin to support these additional bundled modules?

Any docs or blog posts around this would be really helpful.

7

We usually suggest branches per such major IDE versions and issue updates with version suffixes

8

Thank for the reply Yuriy. I suspect our current setup for our plugin is not optimal for keeping up-to-date, that or we are learning the support process for newer IntelliJ versions.

I spent some time updating our intellij platform gradle plugin version (it was previously at 2.2.0, now at 2.9.0) and while that introduced some issues (unrelated to 2025.3’s changes), once solved, our plugin is working fine in 2025.3 and we haven’t needed to add:

bundledModule("intellij.platform.collaborationTools.auth.base") bundledModule("intellij.platform.collaborationTools.auth")

I suspect we will still need to add this at a later stage, but because we’re building against an older version of intellij (242 in our case) I’m guessing something is papering over this differing.

I’m curious if there are docs describing the pieces of the build process that could explain this behavior and I’m also curious if you have seen plugin developers creating different builds of their plugin have a generally smoother experience when supporting larger JetBrains updates?