Stricter plugin verification in IntelliJ Platform Gradle Plugin 2.15.0

Announcements
,
1

As part of our ongoing effort to improve plugin quality and compatibility, the default plugin verification mode is now stricter.
Starting with IntelliJ Platform Gradle Plugin 2.15.0, the verifyPlugin task fails the Gradle build when it detects:

  • plugin compatibility problems with target IDEs,
  • Internal API usage,
  • Override-Only API usage.

How to Opt Out

We understand that some established plugins may still rely on Internal or Override-Only APIs and may not have a quick migration path.
In these cases, you can customize verification behavior by setting failureLevel in the intellijPlatform extension of your Gradle build script.

intellijPlatform {
    pluginVerification {
        failureLevel = listOf(
            FailureLevel.COMPATIBILITY_PROBLEMS,
            FailureLevel.INTERNAL_API_USAGES,
        )
    }
}

By default, failureLevel is now set to:

  • FailureLevel.COMPATIBILITY_PROBLEMS,
  • FailureLevel.INTERNAL_API_USAGES,
  • FailureLevel.OVERRIDE_ONLY_API_USAGES.

JetBrains Marketplace Verification

These changes affect only local Gradle builds.
JetBrains Marketplace verification rules remain unchanged for now.
New plugins are still prohibited from using Internal or Override-Only APIs, and such usage causes verification errors that block publication.

3 Likes
2

I want to highlight that I get a false-positive from OVERRIDE_ONLY_API_USAGES since about one year for LeafOccurrenceMapper.withPointer. See also IJPL-176605 and MP-7233.

1 Like