Hi,
we currently have a GWC api change that is breaking the GeoServer build:
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /var/lib/hudson/jobs/geoserver-2.3.x/workspace/src/gwc/src/main/java/org/geoserver/gwc/layer/GeoServerTileLayer.java:[75,7] org.geoserver.gwc.layer.GeoServerTileLayer is not abstract and does not override abstract method getInfoMimeTypes() in org.geowebcache.layer.TileLayer
[INFO] 1 error
I believe that implementing that method so that it returns null may do the trick (the info mime types are new, so I guess there is some backwards compatibility layer that makes it behave like before if the list is not provided?)
The second worrysome thing is that there is no gwc-master build, and this resulted in a delay of 3 days before we discovered the problem.
I could setup one, and make it so that it triggers the GeoServer master build too, but the computing resources are not mine so I’d at least wait for some confirmation from OpenGeo.
Finally, the topic of releasing GWC. GWC trunk has been part of GeoServer releases and we had no new big issue reported, I also know it has been used in production without again much of an issue so… can we release it?
RC maybe?
What would be the procedure for a GWC release?
What kind of permissions are needed?
Do you think it’s feasible to setup release scripts like the gt/gs ones?
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] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /var/lib/hudson/jobs/geoserver-2.3.x/workspace/src/gwc/src/main/java/org/geoserver/gwc/layer/GeoServerTileLayer.java:[75,7] org.geoserver.gwc.layer.GeoServerTileLayer is not abstract and does not override abstract method getInfoMimeTypes() in org.geowebcache.layer.TileLayer
[INFO] 1 error
I believe that implementing that method so that it returns null may do the trick (the info mime types are new, so I guess there is some backwards compatibility layer that makes it behave like before if the list is not provided?)
The second worrysome thing is that there is no gwc-master build, and this resulted in a delay of 3 days before we discovered the problem.
I could setup one, and make it so that it triggers the GeoServer master build too, but the computing resources are not mine so I’d at least wait for some confirmation from OpenGeo.
Finally, the topic of releasing GWC. GWC trunk has been part of GeoServer releases and we had no new big issue reported, I also know it has been used in production without again much of an issue so… can we release it?
RC maybe?
What would be the procedure for a GWC release?
What kind of permissions are needed?
Do you think it’s feasible to setup release scripts like the gt/gs ones?
Learn Graph Databases - Download FREE O’Reilly Book
“Graph Databases” is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
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-SNAPSHOT, survives this via dependency management, but it is going to break one day (e.g. a backwards-incompatible change in GT 10).
Kind regards,
Ben.
On 13/05/13 03:42, Jody Garnett wrote:
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] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /var/lib/hudson/jobs/geoserver-2.3.x/workspace/src/gwc/src/main/java/org/geoserver/gwc/layer/GeoServerTileLayer.java:[75,7] org.geoserver.gwc.layer.GeoServerTileLayer is not abstract and does not override abstract method getInfoMimeTypes() in org.geowebcache.layer.TileLayer
[INFO] 1 error
I believe that implementing that method so that it returns null may do
the trick (the info mime types are new, so I guess there is some
backwards compatibility layer that makes it behave like before if the
list is not provided?)
The second worrysome thing is that there is no gwc-master build, and
this resulted in a delay of 3 days before we discovered the problem.
I could setup one, and make it so that it triggers the GeoServer
master build too, but the computing resources are not mine so I'd at
least wait for some confirmation from OpenGeo.
Finally, the topic of releasing GWC. GWC trunk has been part of
GeoServer releases and we had no new big issue reported, I also know
it has been used in production without again much of an issue so...
can we release it?
RC maybe?
What would be the procedure for a GWC release?
What kind of permissions are needed?
Do you think it's feasible to setup release scripts like the gt/gs ones?
-------------------------------------------------------
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
<mailto:Geoserver-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
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 right now; we are happy to review this dependency when their availability changes.
Kind regards,
Ben.
On 13/05/13 13:47, Ben Caradoc-Davies wrote:
At the least (in my view) we should make milestone builds of GWC for
stable and master to support GS stable and master.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Build and deployment notes attached. I deployed each artifact by itself to avoid publishing a modified distributionManagement, which would suggest osgeo is the main repo.
Kind regards,
Ben.
On 14/05/13 09:17, Ben Caradoc-Davies wrote:
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 right now; we are happy to
review this dependency when their availability changes.
Kind regards,
Ben.
On 13/05/13 13:47, Ben Caradoc-Davies wrote:
At the least (in my view) we should make milestone builds of GWC for
stable and master to support GS stable and master.
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
Build and deployment notes attached. I deployed each artifact by itself to
avoid publishing a modified distributionManagement, which would suggest
osgeo is the main repo.