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

Aurélien Pupier commented on CAMEL-18341:
-----------------------------------------

it sounds that for Spring Boot it is better to wait Groovy upgrade in Spring 
Boot; Which is [done in 
3.0.0-Mx|https://github.com/spring-projects/spring-boot/issues/31631]. The 
3.0.0 is planned for [end of 
November|[https://github.com/spring-projects/spring-boot/milestone/240]].

For Quarkus, it seems that we should be able to nopt be aligned based 
[https://github.com/quarkusio/quarkus/issues/27111#issuecomment-1203974521] 
Quarkus is not planning to upgrade to Groovy 4.x due to performance regression  
https://issues.apache.org/jira/browse/GROOVY-10307 

> Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x
> --------------------------------------------------------
>
>                 Key: CAMEL-18341
>                 URL: https://issues.apache.org/jira/browse/CAMEL-18341
>             Project: Camel
>          Issue Type: Dependency upgrade
>    Affects Versions: 3.18.0
>            Reporter: Aurélien Pupier
>            Assignee: Aurélien Pupier
>            Priority: Major
>
> Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to 
> move to the latest version.
> There is a long list of features and bug fixes 
> [http://groovy-lang.org/changelogs/changelog-4.0.0.html]
> Maybe worth noticing it contains several fixes related to Java 17:
> * [GROOVY-10391] - Default interface methods causing problems with java 17 
> and groovy 3.0.9
> * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties
> * [GROOVY-10429] - StringBuilder misses setLength method in Java17
> Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two 
> bugfixxes release (in fact already 3 happened). So good chances that there 
> will be only security release of 3.x soon.



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

Reply via email to