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

Ekaterina Dimitrova edited comment on CASSANDRA-18190 at 5/1/23 7:14 PM:
-------------------------------------------------------------------------

Just found this filed javac bug - [https://bugs.openjdk.org/browse/JDK-8215739]

I am not sure we want to blindly ignore options and still keep eclipse only to 
warn on unsafe use of Autocloseable instances

The split package issue sounds like something we need to fix...


was (Author: e.dimitrova):
Just found this filed javac bug - [https://bugs.openjdk.org/browse/JDK-8215739]

I am not sure we want to blindly ignore options and still keep eclipse only to 
warn on unsafe use of Autocloseable instances

> 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