sandynz opened a new issue, #20178: URL: https://github.com/apache/shardingsphere/issues/20178
## Bug Report ### Which version of ShardingSphere did you use? master branch ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? JDBC ### Expected behavior Daily Continuous Integration pass ### Actual behavior https://github.com/apache/shardingsphere/actions/workflows/ci-daily.yml https://github.com/apache/shardingsphere/runs/7828266864?check_suite_focus=true ``` [INFO] Finished at: 2022-08-14T18:14:08Z [INFO] ------------------------------------------------------------------------ Error: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.3.0:jar (attach-javadocs) on project shardingsphere-cluster-mode-repository-zookeeper-curator: MavenReportException: Error while generating Javadoc: Unable to execute javadoc command: Error while executing process. Cannot run program "cmd.exe" (in directory "D:\a\shardingsphere\shardingsphere\shardingsphere-mode\shardingsphere-mode-type\shardingsphere-cluster-mode\shardingsphere-cluster-mode-repository\shardingsphere-cluster-mode-repository-provider\shardingsphere-cluster-mode-repository-zookeeper-curator\target\apidocs"): CreateProcess error=267, The directory name is invalid -> [Help 1] ``` ### Reason analyze (If you can) `CreateProcess error=267, The directory name is invalid`. And there're javadoc passed modules. ``` [INFO] shardingsphere-cluster-mode-core ................... SUCCESS [ 15.147 s] [INFO] shardingsphere-cluster-mode-repository-provider .... SUCCESS [ 0.181 s] [INFO] shardingsphere-cluster-mode-repository-zookeeper-curator FAILURE [ 7.488 s] [INFO] shardingsphere-data-pipeline-core .................. SKIPPED ``` The directory path length is 267, more than 260, maybe it's caused by path length. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. ### Example codes for reproduce this issue (such as a github link). -- 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]
