It is strange to me that your build is *only* looking in Maven-local. You're not building with --offline, are you? Does running with --refresh-dependencies resolve this issue when you have it?
Is anything fiddling with your ~/.m2/repository without updating the corresponding maven xml entries? It seems to me like your local Maven xml records believes it should have an artifact, but then the expected file isn't present on disk. I don't think the forum thread you found is still relevant. That thread points to GRADLE-2709, which has been fixed since Gradle 1.9. All that said, if you don't want to use your local ~/.m2, that's your business. If that folder doesn't exist, the presence of mavenLocal() shouldn't have any effect. But some of us are making use of it. On Wed, May 8, 2019 at 12:24 PM Robert Houghton <rhough...@pivotal.io> wrote: > Jake, my understanding is that benchmarks does not need geode to be able to > pull resources from Maven local. Benchmarks is an external wrapper that > executes geode commands, right? > > On Wed, May 8, 2019, 12:12 Jacob Barrett <jbarr...@pivotal.io> wrote: > > > Maven local is necessary for some of our other build processes like > > benchmarks. > > > > Is there no other way to correct this issue. I have never run into this > > issue. > > > > -jake > > > > > > > On May 8, 2019, at 10:13 AM, Kirk Lund <kl...@apache.org> wrote: > > > > > > I'd like like to remove mavelLocal the Geode gradle files. > > > > > > GEODE-6753: Use of mavenLocal in gradle may cause build to fail with > > > missing tests dependencies > > > https://issues.apache.org/jira/browse/GEODE-6753 > > > > > > Thanks, > > > Kirk > > >
