GeoTools – Which is the Right Maven Repository Version for PostGIS?

geotoolsmaven

The documentation seems to indicate that the right maven repository to use is:

  <repository>
     <id>osgeo</id>
     <name>Open Source Geospatial Foundation Repository</name>
     <url>http://download.osgeo.org/webdav/geotools/</url>
  </repository>

However, it seems that the latest version on this repository was last updated in 2014.
https://mvnrepository.com/artifact/org.geotools.jdbc/gt-jdbc-postgis?repo=osgeo

On the other hand, the Boundless one seems to be carrying a much more updated version than the other repositories. This one was last updated in September 2018:
https://mvnrepository.com/artifact/org.geotools.jdbc/gt-jdbc-postgis/20.0

However, the documentation states that the Boundless repository is for snapshots.

Which is the proper version to use?

Best Answer

The OSGeo repository is the correct one for stable builds (I'm not sure where mvnrepository.com gets its information from) - see http://download.osgeo.org/webdav/geotools/org/geotools/jdbc/gt-jdbc-postgis/20.0/ for the latest PostGIS jar.

Update

Since the demise of Boundless the correct repository for snapshots is:

 <repository>
    <id>osgeo-snapshot</id>
    <name>OSGeo Snapshot Repository</name>
    <url>https://repo.osgeo.org/repository/snapshot/</url>
    <snapshots><enabled>true</enabled></snapshots>
    <releases><enabled>false</enabled></releases>
  </repository>

This is all documented in the Maven Quick start which is the minimum you should read before starting with GeoTools.

Related Solutions

[GIS] Geotools with maven: java.lang.noclassdeffounderror while starting app’s jar

To make a java program run you need to include all of its dependencies on the classpath so that the JVM can find them or include them in the jar itself so that it is truly portable.

In the first case, this can be achieved by adding your maven repository to the command line:

java -jar -cp .:~/.m2/repository/ siveria.avl-1.0-SNAPSHOT.jar

or for the second (and probably better) case you need to create an "uber" or "fat" jar. This combines all the needed jars into one big one that you can execute with no classpath. This is accomplished using the maven shade plugin since this handles the services/spi metadata files that GeoTools uses to handle datastore lookups.

You need to include something like:

<build>
  <plugins>
      <plugin>
          <artifactId>maven-compiler-plugin</artifactId>
          <configuration>
              <encoding>UTF-8</encoding>
              <target>1.8</target>
              <source>1.8</source>
          </configuration>
      </plugin>
      <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-shade-plugin</artifactId>
          <version>1.3.1</version>
          <executions>
              <execution>
                  <phase>package</phase>
                  <goals>
                      <goal>shade</goal>
                  </goals>
                  <configuration>
                      <transformers>
                          <!-- This bit sets the main class for the executable jar as you otherwise -->
                          <!-- would with the assembly plugin                                       -->
                          <transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
                              <manifestEntries>
                                  <Main-Class>org.geotools.demo.Quickstart</Main-Class>
                              </manifestEntries>
                          </transformer>
                          <!-- This bit merges the various GeoTools META-INF/services files         -->
                          <transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
                      </transformers>
                  </configuration>
              </execution>
          </executions>
      </plugin>
  </plugins>
</build>

A final option is to use Maven to execute the program using its knowledge of your dependencies. By including something like and then using mvn exec:java:

         <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>exec-maven-plugin</artifactId>
            <version>1.2.1</version>
            <configuration>
               <mainClass>org.geotools.tutorial.quickstart.Quickstart</mainClass>
               <commandlineArgs>../../data/ne_10m_admin_0_countries.shp</commandlineArgs>
             </configuration>
          </plugin>

[GIS] the correct URL to resolve GeoTools dependencis via Gradle

The repository had to be moved into new environment. The original plan of the GeoTools/GeoServer projects was to use redirections and make the move transparent for the users. Unfortunately maven redirections proofed to be unreliable.

Some links for reading:

http://geotoolsnews.blogspot.com/2020/04/change-to-maven-repositories.html https://www.osgeo.org/foundation-news/new-osgeo-repo/ https://docs.geotools.org/latest/userguide/welcome/upgrade.html

Best Answer

Update

Related Solutions

[GIS] Geotools with maven: java.lang.noclassdeffounderror while starting app’s jar

[GIS] the correct URL to resolve GeoTools dependencis via Gradle

Related Question