[Geoserver-devel] Testing WMS cascading fixes

Hi,
I’m managed to squeeze in some time to look at the cascading issue (mostly by reducing
sleep hours, and a bit by keeping eclipse open in between customer meetings and
madly trying to get something done there), and believe I’ve committed a working solution
for this in geotools.

The next nightly build should have the fixes, can anybody try them out? I probably
won’t have any further time to look at this for the next… hum… 5-7 days.

Also, if anybody could kick the nightly build manually so that we have something
user testable today, that would be great.

Sorry it’s not much, but for this week it’s all I’ve managed to offer :frowning:

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


I have kicked 2.6.x and master nightlies to expedite testing (although I do not think we are still in Andrea's "today").

On 18/09/14 01:52, Andrea Aime wrote:

Also, if anybody could kick the nightly build manually so that we have
something user testable today, that would be great.

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Mineral Resources Flagship
Australian Resources Research Centre

Thanks Andrea, it is mad trying to do volunteer work after foss4g.
I also will be out of touch for a bit, bunch of work to catch up on.

So with these fixes (and a few on master to cherry pick to 2.6.x) we have a final check with Kevin for GWC.

···

Jody Garnett

On Wed, Sep 17, 2014 at 11:52 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
I’m managed to squeeze in some time to look at the cascading issue (mostly by reducing
sleep hours, and a bit by keeping eclipse open in between customer meetings and
madly trying to get something done there), and believe I’ve committed a working solution
for this in geotools.

The next nightly build should have the fixes, can anybody try them out? I probably
won’t have any further time to look at this for the next… hum… 5-7 days.

Also, if anybody could kick the nightly build manually so that we have something
user testable today, that would be great.

Sorry it’s not much, but for this week it’s all I’ve managed to offer :frowning:

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

==

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it



Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk


Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel