————— 2022-5-19 ————— Sargent Ti 11:56 https://linkis.apache.org/en-US/docs/1.1.1/development/linkis_compile_and_package Compile and package the document, do you want to update it to mvnw?
Sargent Ti 12:00 @peacewong@WDS @Weizhong-Xiachen Sargent Ti 12:00 1.1.1-rc2 Sargent Ti 12:03 https://linkis.apache.org/en-US/community/how-to-verify Also here: Verify Release Candidate peacewong@WDS 12:14 Yes, famously, if you can connect to the external network environment, it is recommended to use the mvnw command, because you need to download a plug-in when executing it. Sargent Ti 12:14 I see @weizhong-xiachen says The .mvn/wrapper/maven-wrapper.jar has been removed, but there is no wrapper plugin in the pom, can it be used? Sargent Ti 12:16 We do mvnw to unify the mvn version, right? Then use mvnw uniformly? peacewong@WDS 12:17 Yes, it will use the built-in mvn command Casion 12:17 There is no source package, the script will judge whether it exists, and if it does not exist, it will be downloaded Sargent Ti 12:23 Yes, but the mvnw script should be used uniformly, right? Sargent Ti 12:23 Don't write mvn in the documentation Casion 12:23 One is that you can specify the version of mvn to use, and maven-wrapper is equivalent to an installation-free version of mvn, which supports users to use mvnw in an environment where mvn is not installed separately Sargent Ti 12:24 Don't make it so complicated, and it's easy to come up with the mvnw method without verifying this problem Sargent Ti 12:24 It is recommended to unify, if you want mvn or mvnw Casion 12:24 Hmm, unified default to use mvnw, Sargent Ti 12:24 Otherwise, the compilation and verification have to be run twice. Sargent Ti 12:24 OK New One 12:26 I don't quite understand the difference and scenarios between mvn and mvnw Sargent Ti 12:28 The full name of mvnw is maven wrapper. Its principle is to record the maven version you want to use in the maven-wrapper.properties file. When the user executes the mvnw clean command, it is found that the current user's maven version is inconsistent with the expected version, then download it the desired version, and then execute the mvn command with the desired version Shinichi 12:30 oh oh ————— 2022-5-19 ————— Sargent Ti 11:56 https://linkis.apache.org/zh-CN/docs/1.1.1/development/linkis_compile_and_package 编译打包文档，要不要更新成mvnw？ Sargent Ti 12:00 @peacewong@WDS @微众-夏晨 Sargent Ti 12:00 1.1.1-rc2的 Sargent Ti 12:03 https://linkis.apache.org/zh-CN/community/how-to-verify 还有这里：验证候选版本 peacewong@WDS 12:14 可以的，著名下，如果可以联通外网的环境建议使用mvnw命令，因为执行的时候需要下载一个插件的。 Sargent Ti 12:14 我看@微众-夏晨 说The .mvn/wrapper/maven-wrapper.jar has been removed，但pom里面又没有加wrapper的plugin，这样能用吗？ Sargent Ti 12:16 我们搞mvnw就是为了统一mvn版本对吧？那就统一用mvnw？ peacewong@WDS 12:17 是的，会用内置的mvn命令 casion 12:17 源码包中没有了，脚本中是会判断是否存在，不存在会下载 Sargent Ti 12:23 是，但是统一要用mvnw脚本对吧 Sargent Ti 12:23 就别在文档里写用mvn了 casion 12:23 一个是可以指定使用mvn的版本，另外maven-wrapper相当于一个免安装版本的mvn，支持用户在没有单独安装mvn的环境下通过mvnw使用 Sargent Ti 12:24 别搞这么复杂了，而且也容易再搞出mvnw方式又没验证这种问题 Sargent Ti 12:24 建议统一起来，要就mvn要就mvnw casion 12:24 嗯嗯，统一默认使用mvnw， Sargent Ti 12:24 不然编译验证都得跑2遍 Sargent Ti 12:24 OK 新一 12:26 不太理解 mvn 和 mvnw的区别和场景 Sargent Ti 12:28 mvnw 全名是maven wrapper,它的原理是在maven-wrapper.properties文件中记录你要使用的maven版本，当用户执行mvnw clean 命令时，发现当前用户的maven版本和期望的版本不一致，那么就下载期望的版本，然后用期望的版本来执行mvn命令 新一 12:30 哦哦 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@linkis.apache.org For additional commands, e-mail: dev-h...@linkis.apache.org
