Hello all
To follow-up on this question, is there an interest for experimenting a
replacement of GeoTools dependency (LGPL license) by Apache SIS? (not
knowing in advance if the experiment would be conclusive or not). If
yes, where should be the branch?
Regarding dependencies, by looking at the root pom.xml file [1] I'm a
little bit confused. All non-test dependencies are declared with
<scope>${dependency.scope}</scope> where the ${dependency.scope}
property is set to "provided" be default. This pom.xml file seems to
implement an "all or nothing" behavior regarding dependency scope
management. I would have expected the default scope ("compile") for a
set of dependencies that are essential to Sedona working, and the
"provided" scope for optional dependencies. Are all the dependencies
really optional?
I think that the NOTICE file needs to list the licenses of dependencies.
Maybe [3] can be used as a source of inspiration? Note that gt-epsg is
under EPSG Terms of use, not only LGPL. A similar issue raised for
Apache Calcite goes deeper in this topic and how it can be resolved [4].
I mention those licensing topics because I guess they are the reason for
the way dependencies are declared in the root pom.xml, and if I create a
branch for experimenting some dependencies replacement, understanding
their purposes would be better.
Thanks,
Martin
[1]https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/pom.xml
[2]https://github.com/apache/incubator-sedona/blob/sedona-1.3.1-incubating-rc1/NOTICE
[3]https://github.com/apache/sis/blob/master/NOTICE
[4]https://github.com/locationtech/proj4j/issues/90
