Jakub Chrzanowski
Jakub Chrzanowski
There's a plan to rework dependencies management so everything that is required for building the plugin will be explicitly described in the `dependencies {}` closure of the build script.
Starting with the IntelliJ Platform Gradle Plugin, all dependencies — including the IntelliJ Platform — are defined within the `dependencies {}` block, which makes it possible to control the order....
Implemented in 2.0. All IDEs used by the IntelliJ Plugin Verifier are now handled through the Gradle dependencies management. It is possible to apply the `org.jetbrains.intellij.platform.settings` plugin in `settings.gradle.kts`, which...
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...
@DreierF > Currently the URLs seems to be hardcoded [here](https://github.com/JetBrains/gradle-intellij-plugin/blob/0f38f3ed8fb5eab0f76ac47b1c24e22638a7de9b/src/main/kotlin/org/jetbrains/intellij/tasks/RunPluginVerifierTask.kt#L477). I also don't quite understand why the [releases](https://www.jetbrains.com/intellij-repository/releases) repository is not reused here. Plugin Verifier uses actual IDEs distributions —...
IDEs for IntelliJ Plugin Verifier are now handled through Gradle dependencies with a dedicated extension exposed, see: https://plugins.jetbrains.com/docs/intellij/tools-intellij-platform-gradle-plugin-extension.html#intellijPlatform-verifyPlugin-ides The download URL, or rather a repository from which IDEs are downloaded,...
@aconst-null In some cases, the plugin fetches artifacts from non-Maven repositories – like GitHub or other public resources – using fake Ivy repositories created on-the-fly. How would you see handling...
@aconst-null It won't get auto-closed :) I have to figure out a suitable solution for offline environments. There's no straightforward solution, as we get some artifacts during the task runtime...
Oh. really? That's new to me.
We're supposed to rework the dependencies resolution used by this plugin — I'll put this ticket on hold now as a massive refactoring will be introduced with 2.x version.