linghengqian opened a new issue #13080:
URL: https://github.com/apache/shardingsphere/issues/13080


   ## Question
   
   **For English only**, other languages will not accept.
   
   Before asking a question, make sure you have:
   
   - Googled your question.
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere 
Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot reproduce it on current information, we 
will **close it**.
   
   I noticed that when the project is built with JDK 11, a Groovy warning will 
pop up, and this warning is not displayed when the project is built with JDK 8, 
so I want to confirm whether this is a normal phenomenon?And will the problem 
corresponding to this warning affect the operation of the project? 
   I checked the official Groovy documentation and it seems that this warning 
has been resolved after Groovy 3, but upgrading the version of Groovy does not 
seem to be a good idea to solve this problem.
   ```shell
   WARNING: An illegal reflective access operation has occurred
   WARNING: Illegal reflective access by 
org.codehaus.groovy.reflection.CachedClass 
(file:/D:/xxx/apache-maven-3.8.2/maven-repo/org/codehaus/groovy/groovy/2.4.19/groovy-2.4.19-indy.jar)
 to method java.lang.Object.finalize()
   WARNING: Please consider reporting this to the maintainers of 
org.codehaus.groovy.reflection.CachedClass
   WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
   WARNING: All illegal access operations will be denied in a future release
   ```


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


Reply via email to