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
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
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
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
