味道在于人,就算 java 现在也不需要什么 FileUtils,TimeUtil,都是什么年代的了..nio 的 Files,time 的 Instant 等不够用?
你不会是选择了初始化电脑,然后选择了清除所有数据?
- 清除所有数据,不仅仅是格式化,还会覆盖...(可以设置不清 0)
好熟悉...
没什么好的办法
以前我们是自己开发的一套验证框架..规则基本都是手动写,还要前后端都要加...
Element-Plus table 还是算了...一直都是再引入 vxetable 使用的..
主要是国内网络限制...
你手动执行,也有提示
[2/4] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
你用 maven 多执行几次,可能也会成功,但是那样太慢了...所以手动执行,先把依赖(datacap-ui\node_modules)下载下来...
打开目录 datacap\core\datacap-ui
然后使用在该目录,使用 cmd 执行 yarn --legacy-peer-deps install
这个已经不是 java 与 maven 了,而是前端编译
这个实际是 yarn --legacy-peer-deps install 执行失败了, 应该是前端项目的依赖无法下载把
手动到 datacap-ui 模块执行 yarn --legacy-peer-deps install 试试
<relativePath/>表示 从服务器下载 parent pom
--
<relativePath>../demo-parent/pom.xml</relativePath>
我的环境是就是 idea 24.2, Maven 3.8.5, Jdk 21 ,maven 使用腾讯云的镜像
是不是你的网络有问题,这个项目还有前端项目(datacap-server datacap-ui)需要编译的,会自动下载 node 等,如果没法访问 github 是不行的
mvn compile -U -Dspotbugs.skip -Dgpg.skip -Dcheckstyle.skip -DskipTests=true
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for datacap 2024.3.10-SNAPSHOT:
[INFO]
[INFO] datacap ............................................ SUCCESS [ 21.434 s]
[INFO] datacap-captcha .................................... SUCCESS [ 0.292 s]
[INFO] datacap-fs-spi ..................................... SUCCESS [ 0.062 s]
[INFO] datacap-scheduler-spi .............................. SUCCESS [ 5.759 s]
[INFO] datacap-common ..................................... SUCCESS [ 4.450 s]
[INFO] datacap-client-cli ................................. SUCCESS [ 3.201 s]
[INFO] datacap-parser ..................................... SUCCESS [ 0.127 s]
[INFO] datacap-shaded-pinot ............................... SUCCESS [ 1.962 s]
[INFO] datacap-convert-spi ................................ SUCCESS [ 1.012 s]
[INFO] datacap-convert-txt ................................ SUCCESS [ 1.500 s]
[INFO] datacap-convert-json ............................... SUCCESS [ 1.101 s]
[INFO] datacap-convert-none ............................... SUCCESS [ 0.690 s]
[INFO] datacap-convert-csv ................................ SUCCESS [ 0.695 s]
[INFO] datacap-convert-xml ................................ SUCCESS [ 0.709 s]
[INFO] datacap-spi ........................................ SUCCESS [ 4.657 s]
[INFO] datacap-sql ........................................ SUCCESS [ 1.532 s]
[INFO] datacap-schedule ................................... SUCCESS [ 2.160 s]
[INFO] datacap-parser-spi ................................. SUCCESS [ 0.562 s]
[INFO] datacap-parser-trino ............................... SUCCESS [ 8.260 s]
[INFO] datacap-parser-mysql ............................... SUCCESS [ 16.018 s]
[INFO] datacap-scheduler-local ............................ SUCCESS [ 0.412 s]
[INFO] datacap-executor-spi ............................... SUCCESS [ 0.713 s]
[INFO] datacap-executor-local ............................. SUCCESS [ 0.435 s]
[INFO] datacap-logger ..................................... SUCCESS [ 2.013 s]
[INFO] datacap-shell ...................................... SUCCESS [ 2.330 s]
[INFO] datacap-executor-seatunnel ......................... SUCCESS [ 2.500 s]
[INFO] datacap-service .................................... SUCCESS [ 6.519 s]
[INFO] datacap-security ................................... SUCCESS [ 3.060 s]
[INFO] datacap-jdbc-mysql ................................. SUCCESS [ 2.226 s]
[INFO] datacap-jdbc-clickhouse ............................ SUCCESS [ 2.236 s]
[INFO] datacap-jdbc-presto ................................ SUCCESS [ 2.184 s]
[INFO] datacap-driver-redis ............................... SUCCESS [ 0.048 s]
[INFO] datacap-jdbc-redis ................................. SUCCESS [ 2.249 s]
[INFO] datacap-jdbc-trino ................................. SUCCESS [ 2.567 s]
[INFO] datacap-jdbc-postgresql ............................ SUCCESS [ 2.266 s]
[INFO] datacap-jdbc-elasticsearch ......................... SUCCESS [ 2.277 s]
[INFO] datacap-jdbc-druid ................................. SUCCESS [ 2.245 s]
[INFO] datacap-jdbc-kyuubi ................................ SUCCESS [ 2.232 s]
[INFO] datacap-jdbc-hive .................................. SUCCESS [ 4.242 s]
[INFO] datacap-jdbc-kylin ................................. SUCCESS [ 2.198 s]
[INFO] datacap-jdbc-ignite ................................ SUCCESS [ 2.187 s]
[INFO] datacap-jdbc-db2 ................................... SUCCESS [ 2.354 s]
[INFO] datacap-jdbc-dremio ................................ SUCCESS [ 2.227 s]
[INFO] datacap-jdbc-monetdb ............................... SUCCESS [ 2.136 s]
[INFO] datacap-jdbc-phoenix ............................... SUCCESS [ 6.836 s]
[INFO] datacap-jdbc-h2 .................................... SUCCESS [ 2.117 s]
[INFO] datacap-jdbc-sqlserver ............................. SUCCESS [ 2.139 s]
[INFO] datacap-jdbc-oracle ................................ SUCCESS [ 2.174 s]
[INFO] datacap-jdbc-cratedb ............................... SUCCESS [ 2.256 s]
[INFO] datacap-jdbc-dm .................................... SUCCESS [ 2.117 s]
[INFO] datacap-http-cratedb ............................... SUCCESS [ 2.243 s]
[INFO] datacap-http-clickhouse ............................ SUCCESS [ 2.122 s]
[INFO] datacap-jdbc-tdengine .............................. SUCCESS [ 2.241 s]
[INFO] datacap-jdbc-impala ................................ SUCCESS [ 2.278 s]
[INFO] datacap-jdbc-oceanbase ............................. SUCCESS [ 2.120 s]
[INFO] datacap-native-redis ............................... SUCCESS [ 2.157 s]
[INFO] datacap-jdbc-neo4j ................................. SUCCESS [ 2.175 s]
[INFO] datacap-jdbc-iotdb ................................. SUCCESS [ 2.360 s]
[INFO] datacap-jdbc-snowflake ............................. SUCCESS [ 2.187 s]
[INFO] datacap-shaded-ydb ................................. SUCCESS [ 1.255 s]
[INFO] datacap-jdbc-ydb ................................... SUCCESS [ 2.128 s]
[INFO] datacap-native-zookeeper ........................... SUCCESS [ 2.257 s]
[INFO] datacap-jdbc-duckdb ................................ SUCCESS [ 2.111 s]
[INFO] datacap-native-alioss .............................. SUCCESS [ 2.343 s]
[INFO] datacap-native-kafka ............................... SUCCESS [ 2.204 s]
[INFO] datacap-native-h2 .................................. SUCCESS [ 2.229 s]
[INFO] datacap-http-ceresdb ............................... SUCCESS [ 2.282 s]
[INFO] datacap-http-greptime .............................. SUCCESS [ 2.315 s]
[INFO] datacap-http-questdb ............................... SUCCESS [ 2.283 s]
[INFO] datacap-jdbc-doris ................................. SUCCESS [ 0.357 s]
[INFO] datacap-jdbc-starrocks ............................. SUCCESS [ 0.299 s]
[INFO] datacap-jdbc-hologres .............................. SUCCESS [ 0.312 s]
[INFO] datacap-native-hdfs ................................ SUCCESS [ 0.678 s]
[INFO] datacap-plugin-pinot ............................... SUCCESS [ 0.441 s]
[INFO] datacap-driver-mongo ............................... SUCCESS [ 0.019 s]
[INFO] datacap-plugin-mongo-community ..................... SUCCESS [ 0.318 s]
[INFO] datacap-plugin-cassandra ........................... SUCCESS [ 0.652 s]
[INFO] datacap-plugin-matrixone ........................... SUCCESS [ 0.288 s]
[INFO] datacap-plugin-scylladb ............................ SUCCESS [ 0.434 s]
[INFO] datacap-plugin-paradedb ............................ SUCCESS [ 0.249 s]
[INFO] datacap-plugin-timescale ........................... SUCCESS [ 0.245 s]
[INFO] datacap-plugin-solr ................................ SUCCESS [ 0.262 s]
[INFO] datacap-plugin-influxdb ............................ SUCCESS [ 0.244 s]
[INFO] datacap-fs-local ................................... SUCCESS [ 2.098 s]
[INFO] datacap-fs-qiniu ................................... SUCCESS [ 0.466 s]
[INFO] datacap-fs-alioss .................................. SUCCESS [ 0.429 s]
[INFO] datacap-fs-tencent-cos ............................. SUCCESS [ 0.392 s]
[INFO] datacap-fs-amazon-s3 ............................... SUCCESS [ 0.405 s]
[INFO] datacap-fs-minio ................................... SUCCESS [ 0.458 s]
[INFO] datacap-notify-spi ................................. SUCCESS [ 0.265 s]
[INFO] datacap-http ....................................... SUCCESS [ 2.213 s]
[INFO] datacap-notify-dingtalk ............................ SUCCESS [ 0.314 s]
[INFO] datacap-server ..................................... SUCCESS [01:35 min]
[INFO] datacap-jdbc-mongo ................................. SUCCESS [ 8.526 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 05:07 min
[INFO] Finished at: 2024-09-29T22:14:54+08:00
[INFO] ------------------------------------------------------------------------
一般都是习惯配置好 maven path,直接 mvn compile,有啥错就看看,该跳肯定跳.....
主要是 idea 对 maven 项目导入太慢
这些参数只是跳过一些执行操作.
如果你非要在 idea 中操作,那么
我建议先不用 mvnw,而是在设置中将 maven 指定为自己下载的
> idea 设置中将 maven 指定为 3.7+,另外 maven runner 设置使用项目 jdk
这些参数可以在 idea 的 maven 边栏的工具栏中,有个执行命令的按钮,点击输入 package -Dspotbugs.skip -Dgpg.skip -Dcheckstyle.skip -DskipTests=true 即可
这个项目需要 jdk11 以上
你的 idea 是不是版本太低,里面内置的 maven 版本太低,还是指定了较低版本的 maven?
项目 sdk 设置为 jdk11+
然后 idea 设置中将 maven 指定为 3.7+,另外 maven runner 设置使用项目 jdk
已经测试 idea2024.2 jdk21 正常编译
不差钱 ->阿里云等云提供的 mqtt server
有特殊需求->嵌入 netty mqtt
其它->自己部署 mqtt server
java 10 多年前最流行的框架是 SSH...H 就是 hibernate
项目复杂度,开发时间,人员水平...无法平衡 导致它在国内用的少了.