Re: Remove mavenLocal from Geode gradle files

2019-05-09 Thread Jacob Barrett
geode: ./gradlew installToLocalMaven geode-benchmark: -PgeodeVersion=(version from last build) - Grabs the Geode version from the .m2 repo. > On May 8, 2019, at 12:16 PM, Robert Houghton wrote: > > Jake, my understanding is that benchmarks does not need geode to be able to > pull resources

Re: Remove mavenLocal from Geode gradle files

2019-05-08 Thread Kirk Lund
The following easily reproduces this problem for me: 1) Checkout geode head revision of develop. 2) Create a maven project with these dependencies: junit junit 4.13-beta-3 test org.assertj

Re: Remove mavenLocal from Geode gradle files

2019-05-08 Thread Mark Hanson
Hi Patrick, If our build should not use a local .m2 cache, then we should remove mavenLocal from the build to avoid these possible friction points. I, for one, like the idea of reduce opportunity for problems in the build. If there is a meaningful benefit to having a mavenLocal, then we

Re: Remove mavenLocal from Geode gradle files

2019-05-08 Thread Kirk Lund
I'll assign the bug to you so you can decide if you want to close it or try to fix it... On Wed, May 8, 2019 at 1:26 PM Kirk Lund wrote: > Other people including Barry have run into it as well. > > No, I'm not using --offline, but I will try --refresh-dependencies. The > only thing *weird* that

Re: Remove mavenLocal from Geode gradle files

2019-05-08 Thread Kirk Lund
Other people including Barry have run into it as well. No, I'm not using --offline, but I will try --refresh-dependencies. The only thing *weird* that I'm doing is building a composite build for one of my checkouts. I'm sure I can find a way to fix it for myself if you believe we need to use

Re: Remove mavenLocal from Geode gradle files

2019-05-08 Thread Patrick Rhomberg
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?

Re: Remove mavenLocal from Geode gradle files

2019-05-08 Thread Robert Houghton
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 wrote: > Maven local is necessary for some of our other build processes

Re: Remove mavenLocal from Geode gradle files

2019-05-08 Thread Jacob Barrett
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 wrote: > > I'd like like to remove mavelLocal the Geode gradle files. > > GEODE-6753:

Remove mavenLocal from Geode gradle files

2019-05-08 Thread Kirk Lund
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