Description
Describe the need of your request
With the new IntelliJ Platform Gradle Plugin (2.x
), it’s no longer possible to define custom Maven repositories for resolving IntelliJ Platform dependencies unless they are officially declared via the intellijPlatform {}
block.
In our environment, we do not have direct access to JetBrains repositories (e.g., https://www.jetbrains.com/intellij-repository/releases
). Instead, we proxy them via our internal Maven repository (Artifactory). In plugin version 1.x
, this setup worked fine with standard maven {}
declarations.
Currently, there is no way to use these mirrored repositories with the new plugin.
Proposed solution
Introduce a method similar to customPluginRepository
, for Maven repositories, e.g.:
repositories {
intellijPlatform {
customMavenRepository("https://our-internal-maven-repo/artifactory/maven-intellij-dependencies")
customMavenRepository("https://our-internal-maven-repo/artifactory/maven-jetbrains")
}
}
This would enable environments behind firewalls or proxies to continue using the plugin without needing direct access to JetBrains infrastructure.
Alternatives you've considered
With version 1.x
of the plugin, it was possible to declare:
repositories {
maven {
url = "https://our-internal-maven-repo/artifactory/maven-intellij-dependencies"
}
maven {
url = "https://our-internal-maven-repo/artifactory/maven-jetbrains"
}
}
But these are not picked up by the new plugin 2.x
, which now resolves all IntelliJ-related dependencies via intellijPlatform.repositories
only.
Additional context
No response