I have not experienced this but , for it does take a long time (but not 60min) after an IntelliJ update or invalidating IntelliJ caches. That time it indexes all the Java , maven and gradle caches , sources and jars. Subsequent refreshes are faster. Also increasing IntelliJ memory to 8g helps.
Regards Naba On Wed, Jan 9, 2019 at 6:18 AM Jens Deppe <jensde...@apache.org> wrote: > Is anyone else experiencing very long Gradle refresh times in IntelliJ? > Mine currently takes almost 60 minutes! I'm on IJ 2018.3.2. (I'm pretty > sure that I'm not hitting this problem > > https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_questions_38209851_intellij-2Didea-2Dtakes-2Da-2Dlong-2Dtime-2Dwhen-2Drefreshing-2Da-2Dgradle-2Dproject&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=RhR9iLMRVV3bMiC6y-7JXA&m=XxuxfJ7cNHB5bGsLO0s9zpPOi7B7Dbwbs62QaeO9Uco&s=Wqkgk0evR68m0Y58RX0Qhlyem0P_xQZpb9NRwjEQ2e4&e= > ). > > Actually, it's probably purely a Gradle problem: doing ./gradlew > extensions:geode-modules:dependencies takes 3 1/2 minutes. Multiply that > for every sub-module we have... >