[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #64 was SUCCESSFUL (with 1140 tests). Change made by John Blum .

--- Spring Data GemFire > Nightly-ApacheGeode > #64 was successful. --- Scheduled with changes by John Blum . 1144 tests in total. https://build.spring.io/browse

Re: GEODE-327: Rename gemfire-junit to gemfire-common

Seems reasonable, as long as we tackle it piecewise. Going back to the original purpose, we need a home for @Experimental. We can put that in gemfire-common and create a separate issue for gemfire-junit -> gemfire-test and associated code movement. Anthony > On Sep 12, 2015, at 11:16 AM, Kir

Re: GEODE-327: Rename gemfire-junit to gemfire-common

+1 Jacob Barrett  Manager  GemFire Advanced Customer Engineering (ACE)  Pivotal jbarr...@pivotal.io  503-533-3763 For immediate support please contact Pivotal Support at  http://support.pivotal.io/ On Sat, Sep 12, 2015 at 11:16 AM, Kirk Lund wrote: > I'm pretty sure we could rename gemfire

Re: GEODE-327: Rename gemfire-junit to gemfire-common

I'm pretty sure we could rename gemfire-junit to gemfire-test. gemfire-junit was named only because of gemfire-test existing in a different repo. Currently, all of our reusable testing utilities/classes/rules are under src/test/java in either gemfire-junit or gemfire-core (dunit is all under the l

Re: GEODE-327: Rename gemfire-junit to gemfire-common

Yes, I was originally envisioning creation of a src/main with: src/main/java/com/gemstone/gemfire/annotations/Experimental.java Currently, the purpose of gemfire-junit is to have zero dependencies on other subprojects but provide (currently testing related only) annotations and classes that are u

Re: GEODE-327: Rename gemfire-junit to gemfire-common

You don't want runtime libraries and test time libraries in the same jar. Putting junit utility and annotation classes that would only be used in junits in a jar that would have to be included in a production class path is broken. Gemfire-common.jar would imply something common to gemfire at run

Re: GEODE-327: Rename gemfire-junit to gemfire-common

Can we have ‘src/main’ and ‘src/test’ in proposed gemfire-common and build a gemfire-common-test.jar? So we can separate test utilities from common gemfire utilities. cloudfoundry/UAA…does it with a common-test.jar and other modules with in UAA extend/use common test classes. Sai > On Sep 12

Re: GEODE-327: Rename gemfire-junit to gemfire-common

Annotations are utilities…? The gemfire-junit name seems unnecessarily restrictive. Currently it only contains annotations related to junit tests. Hadoop defines both hadoop-annotations and hadoop-common. Anthony > On Sep 11, 2015, at 9:08 PM, Jacob Barrett wrote: > > -1 > > > > > Rese

Build failed in Jenkins: Geode-nightly #213

See -- [...truncated 187 lines...] :58: warning: S

Re: Apache Geode Interpreter Test on Zeppelin

Hi, Ah young, It is awesome you are giving Goede a try! Sorry for the delayed answer. I'll be traveling next couple of days. So If i understand correct everything is running on a single node? What do you mean by "I connect to the locator the port number 10334 manually.". Can you connect to the