Project Object Model (POM) Files

Complete documentation for the project XML file for Maven can be found at the Maven site, and in particular in the project descriptor part of the reference section.

We only show the things specific to a GeoTools module pom.xml file here.

Extending a Parent Module

The <parent> section allows one pom.xml file to inherit items from another. Modules should extend the pom.xml within the module, plugin, extension or demo directory they belong to:


Artifact Id and GroupId

The combination of id and groupId uniquely identifies each artifact in a maven build.

The id should reflect the name of the module. We use a “gt” prefix to avoid conflicts (as the groupId org.geotools does not appear in the final JAR filenames).


  • gt-main

  • gt-referencing.

This policy allows our gt-main.jar to avoid conflict with an application main.jar created that makes use of GeoTools.

The groupId is initially based reverse domain name org.geotools (following Java package name rules). GeoTools is a multi-module build with each submodule appending to the parent’s groupId.


  • org.geotools

  • org.geotools.plugin

  • org.geotools.extension


Dependencies are specified within the pom.xml file, but care is required to handle this in a consistent manner.

New dependencies on another GeoTools module, should use:

  • groupId - identify the project

  • artifactId - identify the jar within that project

  • version - ${project.version} to match the current build

Sample pom.xml dependency entry:


Dependencies on a third-party jar are defined in two parts.

First the dependency is supplied in the pom.xml file:

     <!-- The version number is specified in the parent POM. -->

Second the dependency version is supplied in the “root” pom.xml file in the dependency management section:


We make use of properties to update multi-module dependencies at the same time: