[
https://issues.apache.org/jira/browse/CALCITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641005#comment-17641005
]
Julian Hyde commented on CALCITE-5399:
--------------------------------------
Reviewing the PR:
* Don't re-order lines in gradle.properties. It creates merge conflicts, and
merge conflicts cause mistakes.
* Do add a comment in gradle.properties for why proj4j cannot be an api
dependency.
I would have asked for a better error than ClassNotFoundException, and a test
that that better error happens, but it seems that Proj4J will fix the licensing
shortly, so that would be overkill. So instead, I think [~bchapuis] should log
a Jira case "Add Proj4J back as a regular dependency" to be fixed in 1.34, and
revisit.
> 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: 2h
> 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)
