[VOTE] Apache Geode release - 1.3.0 RC1

2017-10-12 Thread Swapnil Bawaskar
This is the first release candidate for Apache Geode, version 1.3.0. I will send out a separate vote thread for geode-examples. Thanks to all the community members for their contributions to this release! *** Please download, test and vote by Monday, October 16, 0800 hrs US Pacific. *** It fixes

Re: [VOTE] Apache Geode release - 1.3.0 RC1

2017-10-12 Thread Swapnil Bawaskar
I am cancelling this vote because uploading the archives to maven staging repo failed. The error was: Missing Signature: '/org/apache/geode/apache-geode/1.3.0/apache-geode-1.3.0.tar.gz.asc' does not exist for 'apache-geode-1.3.0.tar.gz' even though that file was created locally. I will dig into it

Re: 1.3.0 release

2017-10-12 Thread Jacob Barrett
All those Geode Native issues you resolved for 1.3 shouldn’t be. I don’t believe we intend to include any native in this release of Geode. > On Oct 11, 2017, at 10:40 PM, Swapnil Bawaskar wrote: > > All issues targeted for 1.3.0 have been resolved. I will cut a release > candidate shortly. > >

Jenkins build is back to normal : Geode-nightly #982

2017-10-12 Thread Apache Jenkins Server
See

Mailing list subscription request

2017-10-12 Thread Arun Yadav
Regards Arun Sent from ProtonMail mobile

Build failed in Jenkins: Geode-nightly-flaky #147

2017-10-12 Thread Apache Jenkins Server
See Changes: [khowe] GEODE_3299: Refactor Gfsh functions to acquire Cache from FunctionContex [kohlmu-pivotal] GEODE-3802: Amending package renaming issues [github] GEODE-3539: consolidate IndexType for bette

Re: Mailing list subscription request

2017-10-12 Thread Anthony Baker
Welcome! Please see [1] for how to subscribe. Anthony [1] http://apache.org/foundation/mailinglists.html > On Oct 12, 2017, at 3:43 AM, Arun Yadav wrote: > > Regards > Arun > > Sent from ProtonMail mobile

Re: [Discuss] Geode gradle plugin

2017-10-12 Thread Anthony Baker
Have you looked at https://plugins.gradle.org/docs/submit ? Anthony > On Oct 11, 2017, at 7:56 PM, Jared Stewart wrote: > > Hi all, > > I've been working on a Gradle plugin to make it easier to write integration > tests for applications that use Apac

Re: [Discuss] Geode gradle plugin

2017-10-12 Thread Jared Stewart
Yeah, the Plugin Portal is great! Not only is it easy to publish to, it also makes the plugin easier to add for users. If you publish to the Portal, a user only needs to add a plugins block: plugins { id 'com.jfrog.bintray' version '0.4.1' } Whereas if you publish to Bintray, JCenter, Mav

ClientProtocolService failures in geode-core dunit

2017-10-12 Thread Kirk Lund
After updating to latest develop, whenever I run a dunit test in geode-core, the dunit locator is now throwing ServiceLoadingFailureException because ClientProtocolServiceLoader can't find a ClientProtocolService provider. It doesn't result in dunit failures (unless the dunit uses the dunit locato

Re: ClientProtocolService failures in geode-core dunit

2017-10-12 Thread Galen O'Sullivan
Yeah, it probably shouldn't be logging the whole stacktrace. I think we should log a message at debug level, and log a warning if a new client tries to connect when the new client protocol isn't available. If we made a "geode-public-API" module, we could avoid the cyclic dependency and do away wit

Re: ClientProtocolService failures in geode-core dunit

2017-10-12 Thread Udo Kohlmeyer
Currently there is a PR awaiting review, that will address this issue. https://github.com/apache/geode/pull/920 On Thu, Oct 12, 2017 at 3:12 PM, Galen O'Sullivan wrote: > Yeah, it probably shouldn't be logging the whole stacktrace. I think we > should log a message at debug level, and log a warn

Re: ClientProtocolService failures in geode-core dunit

2017-10-12 Thread Kirk Lund
I'd recommend "geode-api" (keep the module names and jar names all lower case). On Thu, Oct 12, 2017 at 3:12 PM, Galen O'Sullivan wrote: > Yeah, it probably shouldn't be logging the whole stacktrace. I think we > should log a message at debug level, and log a warning if a new client > tries to c

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

2017-10-12 Thread Spring CI
--- Spring Data GemFire > Nightly-ApacheGeode > #707 was successful. --- Scheduled 2184 tests in total. https://build.spring.io/browse/SGF-NAG-707/ -- This

Failed: jinmeiliao/geode#42 (destroyRegion - b9fb167)

2017-10-12 Thread Travis CI
Build Update for jinmeiliao/geode - Build: #42 Status: Failed Duration: 12 minutes and 52 seconds Commit: b9fb167 (destroyRegion) Author: Jinmei Liao Message: GEODE-2563: destroy region should be idempotent * added the if-exists option for destroy region * ref

Build failed in Jenkins: Geode-release #92

2017-10-12 Thread Apache Jenkins Server
See -- [...truncated 371.77 KB...] at org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:202) at org.apache.geode.cache.client.internal.LocatorTestBase.start

Jenkins build is back to normal : Geode-release-flaky #42

2017-10-12 Thread Apache Jenkins Server
See