On 31/03/16 11:51, Emanuele Tajariol wrote: >> The geoserver-master build now fails because the corresponding changes >> in the geofence 3.1-spring4 branch have not yet been merged: >> https://github.com/geoserver/geofence/tree/3.1-spring4 > Uhm... quite a big change anyway.... > I wonder if it's the case to bump to version 3.2 for geofence. > Definitely we need a strategy for keeping the versions of GeoServer and > GeoFence somehow aligned.
I raised this issue when I noticed the snapshot dependency last year: http://osgeo-org.1560.x6.nabble.com/a-bit-stuck-on-2-9-M0-release-td5242228.html Jody wrote: "we do not need to stress until the beta :)". The beta is passed and beta2 approaches. Turn that smile upside down. :( We could build geofence releases into our release plan, which would allow more easy tracking of snapshots (like geowebcache), or you could make a geofence (for example) 3.1.0 release and the GeoServer community geofence modules could then depend on it. How often does geofence change? How active is development? Kind regards, -- Ben Caradoc-Davies <b...@transient.nz> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
