On Tue, May 14, 2013 at 10:20 AM, Ben Caradoc-Davies <
ben.caradoc-dav...@csiro.au> wrote:
> I deployed a GeoWebCache milestone 1.4-M20130509a to the osgeo repo and
> updated GeoServer master and 2.3.x to use it.
>
> (Second attempt was to get correct revision info in the manifests for the
> GeoSe
I deployed a GeoWebCache milestone 1.4-M20130509a to the osgeo repo and
updated GeoServer master and 2.3.x to use it.
(Second attempt was to get correct revision info in the manifests for
the GeoServer About page. Yes, commit, *then* build. Doh!)
I have published the tag:
https://github.com/b
As discussed at Monday's GeoTools / GeoServer Meeting, I will now make a
GWC milestone with version 1.4-M20130509 and deploy it to the osgeo
repo. This will allow me to fix the GeoServer 2.3.x and master builds
and proceed with this week's release.
We know that the GWC devs are pretty busy righ
At the least (in my view) we should make milestone builds of GWC for
stable and master to support GS stable and master.
I also notice that GWC master (1.4.x) has a dependency (via gwc-wms and
gwc-georss) on GeoTools 9-SNAPSHOT. At the moment, GeoServer master,
which depends on GeoTools 10-SNAPS
Should we collect a tag from before this API change (as a reference point for
release?)
--
Jody Garnett
On Sunday, 12 May 2013 at 12:05 PM, Andrea Aime wrote:
> Hi,
> we currently have a GWC api change that is breaking the GeoServer build:
>
> [INFO] ---
