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:



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 a application “main” jar created that makes use of GeoTools.

Dependency Management

Dependencies are specified within the pom.xml file, but care should be taken 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:


New dependencies on a third-party jar need to be handled in two parts.

The dependency is supplied in the pom.xml file:

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

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

Dependency Version Changes

When a dependency changes you will need to update the root pom.xml “dependency management section” to reflect the new version number.

You should be able to locate an entry like this and change the version number: