Thanks, Jared. I'll try that next time.
On Wed, Jan 23, 2019 at 9:53 AM Jared Stewart
wrote:
> You might also try ./gradlew build --refresh-dependencies if this happens
> again.
>
> On Wed, Jan 23, 2019 at 9:38 AM Kirk Lund wrote:
>
> > I saw the same problem a few weeks ago. I ended up
You might also try ./gradlew build --refresh-dependencies if this happens
again.
On Wed, Jan 23, 2019 at 9:38 AM Kirk Lund wrote:
> I saw the same problem a few weeks ago. I ended up deleting the directories
> in my .m2 repository and rebuilding. That seemed to fix it.
>
> The cause seems to
I saw the same problem a few weeks ago. I ended up deleting the directories
in my .m2 repository and rebuilding. That seemed to fix it.
The cause seems to have something to do with that log4j core tests jar, but
I'm not sure why our build would be looking for the corresponding sources
jar. If
I tried cleaning as well. It turns out that the directory I needed to
remove was `~/.m2`. I guess the package cache was corrupted. Transient
failure?
On Tue, Jan 22, 2019 at 5:49 PM Galen O'Sullivan
wrote:
> I'm getting the following failure building Geode on the latest develop.
> I've tried
I'm getting the following failure building Geode on the latest develop.
I've tried `rm -r .gradle ~/.gradle`, to no avail. Any ideas?
Thanks,
Galen
---
./gradlew dev
> Task :geode-core:compileIntegrationTestJava FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution
