linghengqian opened a new pull request #15303: URL: https://github.com/apache/shardingsphere/pull/15303
Fixes #15277 ,#13080 . Changes proposed in this pull request: - Upgrade `org.codehaus.groovy:groovy:2.5.15` to `org.apache.groovy:groovy:4.0.0`, to provide low-level support for using `Lambda` in row expressions ( Features introduced in Groovy 3.0 , refer to http://groovy-lang.org/releasenotes/groovy-3.0.html ), and handle the `JPMS` issue mentioned in #13080 ( One of the main issues to be resolved in Groovy 4.0 ). - Update LICENSE . - Influenced by the `Classic bytecode generation removal` section of http://groovy-lang.org/releasenotes/groovy-4.0.html , `groovy-indy` is no longer specified. - I have noticed some potential issues with Groovy namespace changes, not sure if it will affect future usage, including but not limited to https://github.com/gradle/gradle/pull/18552 , https://github.com/grails/grails-core/issues/12373 , https://github.com/spring-projects/spring-framework/issues/27985 , I have no experience with Gradle and Grails. So it would be great if a friend could provide experience and examples of Gradle and Grails, so that we can determine whether we should limit the Groovy version to 3.0.9. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
