geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacob Barrett <jbarr...@pivotal.io>
Subject Re: [VOTE] Release candidate for Apache Geode version 1.11.0.RC3.
Date Wed, 04 Dec 2019 19:25:31 GMT


> On Dec 4, 2019, at 9:24 AM, John Blum <jblum@pivotal.io> wrote:
> 
> ´╗┐Anyway, it because Apache Geode's public API is broken/incomplete
> (especially from a framework/tooling perspective, but even an application
> perspective in many cases) that SDG must rely on certain (non-protected)
> "internal" APIs.  It turns out that those "internal" classes have hard
> (i.e. compile-time) dependencies on geode-logging & geode-serialization to
> even build a project (application, framework or otherwise) using those
> classes with Apache Geode.

For those internal classes you use perhaps you can provide an RFC to move them to or augment
the public API? If external things need them we should find a more elegant way to do this
than chasing changing internals.

-Jake


Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message