[
https://issues.apache.org/jira/browse/CALCITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641001#comment-17641001
]
Julian Hyde commented on CALCITE-5399:
--------------------------------------
In [PROJ4J-90|https://github.com/locationtech/proj4j/issues/90], they are
suggesting removing the EPSG data set from the pro4j JAR file. When that is
implemented, it seems to me that proj4j can legitimately be licensed under AL2
with no extra conditions. If that happens, we can revert this change and use
proj4j as a regular dependency.
Do you agree, [~desruisseaux]? (I suspect that the {{org.opengis}} package name
conflict is an orthogonal issue.)
> Proj4j license is not compatible with Apache
> --------------------------------------------
>
> Key: CALCITE-5399
> URL: https://issues.apache.org/jira/browse/CALCITE-5399
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.32.0
> Reporter: Bertil Chapuis
> Assignee: Bertil Chapuis
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.33.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> As explained by [~desruisseaux] in [1], despite being released with an Apache
> compatible license, Proj4j is a problematic dependency. The EPSG codes used
> by Proj4j come with restrictive terms of use [2] and we should find an
> alternative.
> [1] [https://lists.apache.org/thread/2g6j1jx7q5l1sx4mfp1w29obgnvrnvq5]
> [2] [https://epsg.org/terms-of-use.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
