[ 
https://issues.apache.org/jira/browse/CALCITE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638256#comment-17638256
 ] 

Bertil Chapuis edited comment on CALCITE-5399 at 11/24/22 2:00 PM:
-------------------------------------------------------------------

[~julianhyde] Ok, I will make pull request with this change and add 
documentation to the ProjectionTransformer. Regarding release process, should 
the notice be added to the site/develop/index.md file?

[~desruisseaux] Recently, I tried to avoid using reflection, due to the 
complications it introduces when using GraalVM and ahead-of-time compilation. 
From what I understand, Calcite extensively rely on reflection, so this 
shouldn't be a problem. However, even if the classloader work around works 
well, I think it makes developpers hesitant to adopt the geoapi standard.


was (Author: bchapuis):
[~julianhyde] Ok, I will make pull request with this change and add 
documentation to the ProjectionTransformer. Regarding release process, should 
the notice be added to the site/develop/index.md file?

[~desruisseaux] Recently, I tried to avoid using reflection, due to the 
complications it introduces when using GraalVM and ahead-of-time compilation. 
From what I understand, Calcite extensively rely on reflection, so this 
shouldn't be a problem. However, even if the classloader work around works 
well, I think it make developpers hesitant to adopt the geoapi standard.

> 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)

Reply via email to