The geofence codebase is split up into two projects, each with their own
set of properties controlling version numbers:
src/gui.pom.xml
<https://github.com/geoserver/geofence/blob/master/src/gui/pom.xml>
src/services/pom.xml
<https://github.com/geoserver/geofence/blob/master/src/services/pom.xml> (has
model and services-api as children)
I am not sure of the advantage of duplicating here, it does allow the
codebase to produce two distinct projects with slightly different
dependencies.
On the geoserver side the spring-4-upgrade branch has:
community/geofence/pom.xml
<https://github.com/geoserver/geoserver/blob/spring4-upgrade/src/community/geofence/pom.xml>
<dependency>
<groupId>org.geoserver.geofence</groupId>
<artifactId>geofence-services-api</artifactId>
<version>${gf.version}</version>
</dependency>
<dependency>
<groupId>org.geoserver.geofence</groupId>
<artifactId>geofence-model</artifactId>
<version>${gf.version}</version>
</dependency>
community/geofence-server/pom.xml
<https://github.com/geoserver/geoserver/blob/spring4-upgrade/src/community/geofence-server/pom.xml>
<dependency>
<groupId>org.geoserver.geofence</groupId>
<artifactId>geofence-services-impl</artifactId>
<version>${gf.version}</version>
</dependency>
--
Jody Garnett
--
Jody Garnett
On 21 March 2016 at 16:03, Jody Garnett <jody.garn...@gmail.com> wrote:
> I am not quite sure on how we manage the geofence project, from the README
> I should take developer questions here.
>
> I would like to start a spring-4-upgrade branch, coordinating with any
> interested developers here.
>
------------------------------------------------------------------------------
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=278785351&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
