'dependencies.dependency.version' for org.testng:testng:jar is either LATEST or RELEASE (both of them are being deprecated)
前言
执行Maven → "son-project-1" → Lifecycle → package,
总会有警告信息,
'dependencies.dependency.version' for org.testng:testng:jar is either LATEST or RELEASE (both of them are being deprecated)
找到提示的项目的pom.xml,
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>RELEASE</version>
<scope>test</scope>
</dependency>
找到原因
搜索相关错误信息,找到Stackoverflow上关于此的一些信息↓
We had a similar situation: We have parent poms that are used by hundreds of projects by dozens of developers. In Ant, we had an approach similar to the RELEASE one, but now we have explicit version numbers.
Every developer needs to run versions:update-parent to get the new version, otherwise he/she stays with the old one. The disadvantage is that several versions of the parent pom are in use, the advantage is build stability because the "parent pom people" cannot destroy the builds by a wrong configuration that is drawn implicitly.
In your case, I would advice you to think whether you really need everybody to use the same version. If you really need this, you probably have to use version ranges as [1.0.0,)
根据我的英语水平 + 谷歌翻译后,
我理解的就是不能直接指定版本为"RELEASE",
而应该指定一个确定的版本号 . . .
解决方案
打开该项目的pom.xml,将鼠标移至RELEASE上,
等待显示该发布版本的具体信息,
( 我这里的发布版本其实就是7.4.0 )
将RELEASE修改为7.4.0
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>7.4.0</version>
<scope>test</scope>
</dependency>
再次执行Maven → "son-project-1" → Lifecycle → package ,
不报警告了 . . .
完美؏؏☝ᖗ乛◡乛ᖘ☝؏؏
