[
https://issues.apache.org/jira/browse/CALCITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637861#comment-17637861
]
Julian Hyde commented on CALCITE-5399:
--------------------------------------
I agree this is a problem. LEGAL-183 concludes that projects such as SIS can
depend on the EPSG data as along as the user explicitly agrees. As
server/library software, Calcite has no opportunity to ask fir the users
permission.
Also, the “no commercial use” provisions seem at odds with the Apache license.
I am angry that Proj4j uses the Apache license. They basically shipped us a
time bomb.
Bertil suggests using a “provided” dependency. I believe that only works,
legally, if there is an alternative that allows the software to work. A
possible solution might be a stub library that implements Proj4j’s API, has
reduced functionality, and can be replaced by the user (what maven calls
“provided”) if they agree to EPSG’s terms. We could build this in Calcite, but
it really should have been done by Proj4j.
> Proj4j license is not compatible with Apache
> --------------------------------------------
>
> Key: CALCITE-5399
> URL: https://issues.apache.org/jira/browse/CALCITE-5399
> Project: Calcite
> Issue Type: Bug
> Reporter: Bertil Chapuis
> Priority: Major
>
> 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 and we should find an
> alternative.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
