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

Ekaterina Dimitrova edited comment on CASSANDRA-18190 at 5/2/23 10:13 AM:
--------------------------------------------------------------------------

We were considering to compare and possibly substitute with Google ErrorProne. 

According to the ErrorProne instruction 
[here|https://errorprone.info/docs/installation], we would need these artifacts:
 * {{error_prone_core-${EP_VERSION?}-with-dependencies.jar}} 
from[https://repo1.maven.org/maven2/com/google/errorprone/error_prone_core/]
 * {{dataflow-errorprone-${DATAFLOW_VERSION}.jar}} 
from[https://repo1.maven.org/maven2/org/checkerframework/dataflow-errorprone/]

Unfortunately dataflow-errorprovne is GPL2 license so I think in this case we 
are not allowed to use ErrorProne if I am reading correctly 
[here|https://www.apache.org/licenses/GPL-compatibility.html]

According to the ECJ issues I was seeing, except asking about our setup, I did 
not receive an advice at the eclipse forum. Though after experimenting and 
reading more I think the syntax errors are probably only because of not 
properly set properties. I will try to deal with that


was (Author: e.dimitrova):
We were considering to compare and possibly substitute with Google ErrorProne. 

According to the ErrorProne instruction 
[here|https://errorprone.info/docs/installation], we would need these artifacts:
 * {{error_prone_core-${EP_VERSION?}-with-dependencies.jar}} 
from[https://repo1.maven.org/maven2/com/google/errorprone/error_prone_core/]
 * {{dataflow-errorprone-${DATAFLOW_VERSION}.jar}} 
from[https://repo1.maven.org/maven2/org/checkerframework/dataflow-errorprone/]

Unfortunately dataflow-errorprovne is GPL2 license so I think in this case we 
are not allowed to use ErrorProne if I am reading correctly 
[here|https://www.apache.org/licenses/GPL-compatibility.html]

According to the ECJ issues I was seeing, except asking about our setup, I did 
not receive an advice. Though after experimenting and reading more I think the 
syntax errors are probably only because of not properly set properties. I will 
try to deal with that

> ECJ upgrade
> -----------
>
>                 Key: CASSANDRA-18190
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18190
>             Project: Cassandra
>          Issue Type: Task
>          Components: Feature/UDF
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 5.x
>
>
> During testing it was identified that we will need to update ECJ for the Java 
> UDF functions in order to bring Java 17 in.
> It seems the compiler artifacts are moved from 
> [here|https://mvnrepository.com/artifact/org.eclipse.jdt.core.compiler/ecj ] 
> to [here|https://mvnrepository.com/artifact/org.eclipse.jdt/ecj] and there is 
> change of license from EPL1.0 to EPL2.0 too. But if I read correctly 
> [here|https://www.apache.org/legal/resolved.html#weak-copyleft-licenses] that 
> should not affect us
> Further testing and review of all changes between artifacts to be done.
> ECJ is used for the eclipse-warnings and Java UDFs



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to