Jin>Some of my users write tests based on functionalities provided from Calcite Jin>test framework
Frankly speaking, it was somewhat surprising for me, and it does bring extra demand for having a proper calcite-test-framework. The naming is hard, however, I would suggest artifactId=calcite-test-framework. Any thoughts? It turns out Flink depends on Calcite's test code like FlinkSqlParserImplTest extends calcite.SqlParserTest: https://issues.apache.org/jira/browse/CALCITE-2905?focusedCommentId=17002741&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17002741 For instance, a year or so ago I refactored SqlTestFactory (for enabling SqlAdvisor tests) in https://github.com/apache/calcite/commit/96b28f7ba11de22a68d984de6b6b88311cc2c57e , and I was not expecting that someone else might use that test code Vladimir