Jake helped me figure this out... Turned out I had shiro artifacts in my local maven cache (in addition to gradle cache). I'm not sure exactly *how* the maven shiro artifact was broken, but after deleting ~/.m2/repository/org/apache/shiro, everything started to work again.
On Wed, Jan 9, 2019 at 6:32 AM Jens Deppe <jde...@pivotal.io> wrote: > Maybe it's just my system, but this commit seems to have introduced the > problem for me: > > 411b22cdd1d87f1c55f81de948ff36f421a893af - GEODE-6198: Add > geode-all-bom for dependency versioning (#2995) > > As an aside (but possibly related) a get a bunch of these messages during > a build: > > [Fatal Error] shiro-core-1.4.0.pom:2:10: Already seen doctype. > > Turns out they're not fatal though because the build still succeeds. > > I have also done the usual: delete Gradle caches, re-import project, etc., > etc. > > --Jens > > On Wed, Jan 9, 2019 at 6:26 AM Jacob Barrett <jbarr...@pivotal.io> wrote: > >> I had a similar issue about 3 months ago where Gradle would just crawl. I >> tried many things with no luck. Eventually I just deleted all the Gradle >> ‘build’ directories and the Gradle cache and problem went away. >> >> -Jake >> >> >> > On Jan 9, 2019, at 6:23 AM, Nabarun Nag <n...@pivotal.io> wrote: >> > >> > 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... >> >> >> >>
