IntelliJ Platform 2.2.1 JBR

已计划

Is there a way to prevent the JBR being downloaded?

I have tried adding `jetbrainsRuntimeLocal` in the dependencies to point to a local copy of JBR

e.g.

dependencies {
	intellijPlatform {
		intellijIdeaCommunity "242.21829.142", false
		jetbrainsRuntimeLocal(jbrHome)
	}
}

but it still tries to download the JBR from jetbrainsRuntime() repo as well during the build.  

Also,  does the jetbrainsRuntime() point to a maven repository? 

0

Trying to build a plugin within a CI/CD environment that doesn't have access to the external resources i.e. JBR, so I want to be able to set the JBR manually from an internal location.

Also, oddly if I set `org.jetbrains.intellij.platform.useCacheRedirector=false` in gradle.properties.  It still tries to download the JBR using cache-redirector.

This is the error I get, even if I try setting the JBR using `org.gradle.java.home` and` jetbrainsRuntimeLocal()` 
 

Could not determine the dependencies of task ':verifyPluginProjectConfiguration'.
> Could not resolve all task dependencies for configuration ':jetbrainsRuntime'.
   > Could not resolve com.jetbrains:jbr:jbr_jcef-21.0.3-linux-x64-b509.11.
     Required by:
         project :
      > Could not resolve com.jetbrains:jbr:jbr_jcef-21.0.3-linux-x64-b509.11.
         > Could not get resource 'https://cache-redirector.jetbrains.com/intellij-jbr/jbr_jcef-21.0.3-linux-x64-b509.11.tar.gz'.
            > Could not HEAD 'https://cache-redirector.jetbrains.com/intellij-jbr/jbr_jcef-21.0.3-linux-x64-b509.11.tar.gz'. Received status code 503 from server: Service Unavailable


The only workaround I could find was to exclude the JBR from the configuration

configurations.all {
exclude group: 'com.jetbrains', module: 'jbr'
}

Would be good though, if using  `jetbrainsRuntimeLocal` then JBR download attempt does not occur

 

0

or just like setting some gradle properties productsReleasesAndroidStudioUrl and productsReleasesJetBrainsIdesUrl for patch status check to get resource 'https://www.jetbrains.com/updates/updates.xml', if so, we can set a proxy configuration to make our CI/CD environment work, as you know, which doesn't have access to the external resources, that is, provide a gradle property chance to pointing where to download JBR, we can use it to our proxy URL and redirect to your site. On the other hands, it's also good for us to publish JBR to Maven Central, but as it said in https://github.com/JetBrains/intellij-platform-gradle-plugin/issues/1402, you don't plan to publish JBR to Maven Central.

0

请先登录再写评论。