Jakub Chrzanowski

With the IntelliJ Platform Gradle Plugin 2.0 release, the repository and dependency management is now changed. Every IntelliJ Platform is treated as an explicit dependency, which is fetched from the...

Looks like we need to rework dependencies management to something less magical.

Implemented in 2.0. It is possible to apply the `org.jetbrains.intellij.platform.settings` plugin in `settings.gradle.kts`, which also provides a set for repository helpers to let you add all necessary repositories to the...

Is it reproducible in 4.5.1?

Running tests using different IntelliJ Platform is now possible with the 2.0 release. See: https://plugins.jetbrains.com/docs/intellij/tools-intellij-platform-gradle-plugin-tasks.html#testIde

Running tests using different IntelliJ Platform is now possible with the 2.0 release. ```kotlin import org.jetbrains.intellij.platform.gradle.IntelliJPlatformType import org.jetbrains.intellij.platform.gradle.tasks.TestIdeTask tasks { val testPhpStorm by registering(TestIdeTask::class) { type = IntelliJPlatformType.PhpStorm version =...

The 2.0 fully relies on the information provided with `product-info.json` file and uses bundled JBR, if available.

Starting with the IntelliJ Platform Gradle Plugin 2.0, it is possible to declare multiple `runIde`-like tasks to run different IDE instances with your plugin loaded, by extending the `RunIdeTask` task...

Can you please check it with `1.12.3-SNAPSHOT`?

Ok, I will investigate it next week. Should I use the main branch or something else? A brief repro scenario would be welcome.