---
Spring Data GemFire > Nightly-ApacheGeode > #893 was successful.
---
Scheduled
2386 tests in total.
https://build.spring.io/browse/SGF-NAG-893/
--
This
I can help with that.
On Fri, Apr 20, 2018 at 1:46 PM, Anthony Baker wrote:
> I surfed through our JIRA backlog and cleaned up a bunch of old
> issues—primarily issues that we missed resolving when the fix was made. In
> some cases I asked for help determining if the issue should be closed. I
I surfed through our JIRA backlog and cleaned up a bunch of old
issues—primarily issues that we missed resolving when the fix was made. In
some cases I asked for help determining if the issue should be closed. If you
got one of these requests please try and follow up in the next week or so and
I’ve just addressed GEODE-5030 [1] by cleaning up geode releases prior to 2018.
These older versions are still available from
http://archive.apache.org/dist/geode/.
Anthony
[1] https://issues.apache.org/jira/browse/GEODE-5030
FYI, I’ve filed https://issues.apache.org/jira/browse/INFRA-16409 to allow us
to better integrate concourse and GitHub PR”s.
Anthony
Perhaps a reference to the "experimental" interface would be helpful. This
"specification" page (
https://cwiki.apache.org/confluence/display/GEODE/Public+Interface+to+Cluster+Configuration+Service)
contains
no links.
*Main question... again, why should the ClusterConfigurationService
interface h
Perhaps org.apache.geode.DataSerializable or
org.apache.geode.internal.DataSerializableFixedID instead of
java.io.Serializable?
Sarge
> On 19 Apr, 2018, at 17:04, Patrick Rhomberg wrote:
>
> E) Every cluster configuration object should be Serializable so that the
> objects may be sent from lo
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.6.0/jobs/DistributedTest/builds/10
