Uploaded image for project: 'GeoTools'
  1. GEOT-6341

gt-epsg-hsql gets dragged in by gt-wmts through gt-tile-client

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Fixed
    • Affects versions: 21.2, 22-RC
    • Fix versions: 21.3
    • Components: tile-client, WMTS
    • Labels:
      None
    • Environment:

      want to use wkt EPSG authority and not hslq

      Description

      We've got an application where we prefer to use the gt-epsg-wkt artifact, but it is also using the gt-wmts artifact which has dependency on gt-tile-client which has gt-epsg-hsql as a dependency so we end up with both the wkt as well as the hsql version in our final package; it doesn't seem to cause any problems (I don't see any Factory exceptions that the FAQ talks about [1]) but I would think that the tile client should be using a different scope for the epsg library (eg. test like the gt-wms module) because it makes it hard to choose a certain EPSG over the hsql version. (yes I can - as a workaround - add exclusions in my projects pom file)

      mvn dependency:tree snippet:

      [INFO] +- org.geotools:gt-wmts:jar:21.2:compile
      [INFO] |  +- org.geotools:gt-tile-client:jar:21.2:compile
      [INFO] |  |  +- org.geotools:gt-epsg-hsql:jar:21.2:compile
      [INFO] |  |  \- commons-httpclient:commons-httpclient:jar:3.1:compile 
      

      Section in the tile-client pom:
      https://github.com/geotools/geotools/blob/22c9e4a80aff47731feb174b97c5dbef3dc373b0/modules/extension/tile-client/pom.xml#L84-L88

      [1] https://docs.geotools.org/latest/userguide/library/referencing/faq.html#q-how-to-choose-an-epsg-authority

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mprins Mark Prins
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: