Emanuele, we discussed the GeoFence SNAPSHOT dependency at today's committee meeting. As the GeoServer modules are community modules, there is no prohibition on SNAPSHOT dependencies, but we recommend using release dependencies to improve reproducibility and maintainability. Would you consider making a (for example) GeoFence 3.2.0 release and updating the GeoServer modules to depend it before GeoServer 2.9-beta2?
Kind regards, Ben. On 01/04/16 10:03, Ben Caradoc-Davies wrote: > Thanks, Emanuele. We will probably need a release of geofence for > GeoServer 2.9-beta2 and later releases. I am not sure how strict we > should be with community module dependencies. The committee should > discuss at the meeting next week. > > Kind regards, > Ben. > > On 01/04/16 00:46, Emanuele Tajariol wrote: >> Hi, >> >> - branched geofence 3.1.x (Geoserver 2.8 depends on it) >> - merged the spring4 branch onto master >> - bumped geofence master to 3.2-SNAPSHOT >> - fixed the geofence deploy on ares (the jenkins job was not deploying the >> artifacts ) >> - bumped the geofence dep on geoserver to 3.2-SNAPSHOT >> >> Jenkins seems to be quite satisfied at the moment for both geofence-master >> and >> geoserver-master :) >> >> Cheers, >> Emanuele > -- Ben Caradoc-Davies <b...@transient.nz> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
