ok I see Kevin fixed it at 355a287ff9dae5156ec9b6b19c78d8e641312ec7 already
On Tue, May 12, 2015 at 3:47 PM, Gabriel Roldan
wrote:
>
>
> On Tue, May 12, 2015 at 3:43 PM, Gabriel Roldan
> wrote:
>
>> Hi I didn't know I had to check that module, sorry. Took care of removing
>> the calls from the
On Tue, May 12, 2015 at 3:43 PM, Gabriel Roldan
wrote:
> Hi I didn't know I had to check that module, sorry. Took care of removing
> the calls from the gwc module before the update to gwc. Fixing the
> hz-cluster module now.
>
I mean, gwc-distributed.
>
> On Tue, May 12, 2015 at 11:10 AM, Andrea
Hi I didn't know I had to check that module, sorry. Took care of removing
the calls from the gwc module before the update to gwc. Fixing the
hz-cluster module now.
On Tue, May 12, 2015 at 11:10 AM, Andrea Aime
wrote:
> Hi,
> yesterday a change in GWC TileObject API
> caused the GeoServer Hazelca
A test in the Hazelcast Caching module is calling some of the methods that
Gabriel removed. It looks like it just requires removing those calls as
they don't represent the actual behaviour of GWC that they are meant to be
mocking.
On 12 May 2015 at 07:10, Andrea Aime wrote:
> Hi,
> yesterday a
Hi,
yesterday a change in GWC TileObject API
caused the GeoServer Hazelcast based distributed in memory cache to fail
compilation:
https://github.com/GeoWebCache/geowebcache/commit/af3d205205a5540a52115c76f7dc95fb938deac5
Can anybody have a look?
Cheers
Andrea
--
==
GeoServer Professional Ser
