> 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. Cheers, Emanuele Alle 00:00:34 di Thursday 31 March 2016, Ben Caradoc-Davies ha scritto: > On 31/03/16 05:59, Emanuele Tajariol wrote: > >> Can you apply this fix to master and we can delete the spring-4-upgrade > >> branch. > > > > Sure, > > here it is > > <https://github.com/geoserver/geoserver/commit/9473b585770f068ec0c1374e68 > > f19ddb13d8e8ef> > > > > Cheers, > > Emanuele > > 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 > > Build failure: > http://ares.boundlessgeo.com/jenkins/job/geoserver-master/2346/changes > > Kind regards, -- == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information. == Ing. Emanuele Tajariol Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 380 2116282 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- ------------------------------------------------------------------------------ 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
