Jakub Chrzanowski

With the IntelliJ Platform Gradle Plugin 2.0, the IntelliJ Platform along with all plugins (bundled or plugins from JetBrains Marketplace) are added to the project as regular dependencies in the...

Extracting IDEs downloading into a separated task is the way to go.

With the 2.0 release, IDEs used by the IntelliJ Plugin Verifier are managed by the Gradle dependencies mechanism. That will let Gradle handle this scenario with ease.

In the 2.0 release, I've redesigned how the JBR is resolved and how you can configure it for your project. Could we focus on that release? It'd be great if...

The `runPluginVerifier` was renamed to `verifyPlugin`, but you noticed that already. Is this solution involving `RuntimeAware`-based tasks reconfiguration suitable for you? Actually, this is one of reasons why such `*Aware`...

Ok, I went an extra mile here. ;) Since `2.0.0-beta9`, it'll be possible to specify the local path to JetBrains Runtime via dependencies, so in your case that'd be: ```...

Indeed, enabling the source download is necessary since `2022.2` and `2022.3` now, as @Undin mentioned above. I'm aware of this inconvenience and will try to address that with DevKit enhancement...

Here is a quick summary of what was recently done in plugin development tooling regarding downloading IntelliJ Platform sources: **Gradle IntelliJ Plugin 1.x** The `intellij.downloadSources` property, responsible for downloading `IC`...

Can't reproduce on `1.13.1-SNAPSHOT` — could you please verify if this problem is still valid?

We do not plan to publish JBR to Maven Central. With the `2.0` release, the dependency management is now reworked, so you'll be able to manually build the location where...