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
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 Err
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 wrote:
>
> I have not experience
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.
Re
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://stackoverflow.com/questions/38209851/intellij-idea-takes-a-long-time-when-refreshing-a-gradle-project
).
Ac
