[
https://issues.apache.org/jira/browse/CALCITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638008#comment-17638008
]
Julian Hyde commented on CALCITE-5399:
--------------------------------------
[~bchapuis], Yes, that sounds sufficient. To be safe, I would add a step to the
release process to manually check that proj4j is not among the dependencies.
The one and only Calcite class that uses proj4j is {{ProjectionTransformer}}.
It is possible that in future, some other code in Calcite references that
class, causes it to load, and causes the {{ClassNotFoundException}} to be
thrown. The documentation of {{ProjectionTransformer}} should explain its
peculiar licensing and linking situation.
> 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: Major
> Fix For: 1.33.0
>
>
> 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)
