Re: [DISCUSS] Benchmarks module package structure

The package might be always a problem. Even you put the cq benchmark code under geode-cq to near its source code, it might still have to access code under other package, such as geode-core. So I think put benchmark test code under benchmark package is ok. Your option 2) is good. Regards Gester O

[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #790 was SUCCESSFUL (with 2324 tests)

--- Spring Data GemFire > Nightly-ApacheGeode > #790 was successful. --- Scheduled 2326 tests in total. https://build.spring.io/browse/SGF-NAG-790/ -- This

Build failed in Jenkins: Geode-release #103

See -- [...truncated 184.63 KB...] :geode-common:processTestResources NO-SOURCE :geode-common:testClasses :geode-common:checkMissedTests :geode-common:spotlessJavaCheck :geode-common:spotless